Bug 18383 - drakdisk crashed (current_hd called but $current_kind is not an hd)
Summary: drakdisk crashed (current_hd called but $current_kind is not an hd)
Status: RESOLVED DUPLICATE of bug 5801
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2016-05-06 10:21 CEST by Sabrina Gottlieb
Modified: 2016-07-28 08:49 CEST (History)
2 users (show)

See Also:
Source RPM: drakxtools-17.19-3.mga6
CVE:
Status comment:


Attachments

Description Sabrina Gottlieb 2016-05-06 10:21:28 CEST
The "drakdisk" program crashed. Drakbug-17.19 caught it.

Partitionen verwalten . Dasselbe Problem beim Installieren . drakdisk zeigt keine Partitionen an !!! 
Das Partitionsfeld ist leer .
Beim Installieren geht (daher?) nur "gesamte Platte verwenden" 
Nebenbei: Beim Starten erscheint zweimal "failed to get cgroup: no medium found" , weià nicht was cgroup is . 

current_hd called but $current_kind is not an hd () at /usr/lib/libDrakX/diskdrake/hd_gtk.pm line 408.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.0/Gtk3.pm:524
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1530
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:859
ugtk3::main() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:131
diskdrake::hd_gtk::main() called from /usr/libexec/drakdisk:93

Theme name: Adwaita
Kernel version = 4.4.5-server-1.mga6
Distribution=Mageia release 6 (Cauldron) for x86_64
CPU=AMD FX(tm)-8320 Eight-Core Processor
Comment 1 Marja Van Waes 2016-05-06 14:48:11 CEST
The crash might be a duplicate of bug 5801, if this is about RAID... is it?

If not then it is bug 18076 which got fixed after Mageia 6 dev1 was released.
You should no longer get this crash after updating your system.

The invisible partitions issue was fixed, see bug 17564
However, that fix was not included on the Mageia6dev1 isos, either. The partitions should be visible after updating your system.

Please report back.

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Source RPM: drakxtools-curses-17.19-3.mga6 => drakxtools-17.19-3.mga6

Comment 2 Sabrina Gottlieb 2016-05-07 10:10:37 CEST
No RAID , i've never used this in 25 years . 

The bug is not only on installing . 
Clicking on partition type (f.e. "ext4") the partitions don't appear . 
Next step: Deleting all partitions (the whole disk) the PC restarts . After that the same bug occurs again . But using "install on whole disk" now functioned . 

Other bug: Choosing all available desktops to install was no problem .

#
I've sended the bugreport , i logged out , i clicked on the right button , an window appears with the mouse-"X" . Then shutting down . Today i have the problem , the mouse is an "X" , i can not get into the system now. Sorry.
Comment 3 Sabrina Gottlieb 2016-05-07 10:14:32 CEST
(In reply to Marja van Waes from comment #1)
> The crash might be a duplicate of bug 5801, if this is about RAID... is it?
> 
> If not then it is bug 18076 which got fixed after Mageia 6 dev1 was released.
> You should no longer get this crash after updating your system.
> 
> The invisible partitions issue was fixed, see bug 17564
> However, that fix was not included on the Mageia6dev1 isos, either. The
> partitions should be visible after updating your system.
> 
> Please report back.

Sorry i've made only a comment instead of reply .
Comment 4 Sabrina Gottlieb 2016-05-07 10:25:58 CEST
It seems to be the same bug as 17564 , i don't remember exactly , but i think the "expert mode" on installed system causes my bugreport . On the most time i use expert-mode .
Comment 5 Marja Van Waes 2016-05-07 13:44:21 CEST
(In reply to Sabrina Gottlieb from comment #2)

> Today i have the
> problem , the mouse is an "X" , i can not get into the system now. Sorry.

That's sad :-(
Please ask in the forums for help https://forums.mageia.org/de/ If the 'mouse is an "X"'-issue persists after fully updating your system, then please file a separate bug report if a bug report does not already exist.

I'll close this report as duplicate of bug 18076. Please reopen if you still get the crash with diskdrake from drakxtools-17.29-1.mga6 or newer.

*** This bug has been marked as a duplicate of bug 18076 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 6 Marja Van Waes 2016-05-07 17:34:24 CEST
(In reply to Marja van Waes from comment #5)

> 
> *** This bug has been marked as a duplicate of bug 18076 ***

Sorry, I had too many tabs open in Firefox and mixed up bug reports.

the "$current_kind is not an hd bug" is a different one, don't have time to search now.

However, please do report  whether you still
 get the crash with diskdrake from drakxtools-17.29-1.mga6 or newer.

Status: RESOLVED => REOPENED
Resolution: DUPLICATE => (none)

Comment 7 Sabrina Gottlieb 2016-05-07 18:25:18 CEST
No problem . 

> the "$current_kind is not an hd bug" is a different one, don't have time to
> search now.

Is not a different one . I get the same message again and again . 
After an unhappy hdd-crash i changed to another IDE-hdd and got the same message again . So, not a hdd-problem .
 
>  get the crash with diskdrake from drakxtools-17.29-1.mga6 or newer. 
drakxtools is the SAME as in mga6-dev1.ISO 
No version available . I cannot get into the system because of mouse "X".
Thierry Vignaud 2016-07-12 02:14:55 CEST

CC: (none) => thierry.vignaud
Summary: drakdisk crashed => drakdisk crashed (current_hd called but $current_kind is not an hd)

Comment 8 Marja Van Waes 2016-07-28 08:44:48 CEST
(In reply to Sabrina Gottlieb from comment #7)
> No problem . 
> 
> > the "$current_kind is not an hd bug" is a different one, don't have time to
> > search now.
> 
> Is not a different one

So this should be fixed with the 6sta1 isos, because they came with the fix for bug 18076.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Comment 9 Thierry Vignaud 2016-07-28 08:49:15 CEST
I don't think so.

*** This bug has been marked as a duplicate of bug 5801 ***

Resolution: FIXED => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.