Bug 16136 - drakdisk crashed (current_hd called but $current_kind is not an hd (raid) at /usr/lib/libDrakX/diskdrake/hd_gtk.pm line 406)
Summary: drakdisk crashed (current_hd called but $current_kind is not an hd (raid) at ...
Status: RESOLVED DUPLICATE of bug 5801
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-16 23:54 CEST by Gabriel Gazzan
Modified: 2015-06-17 12:52 CEST (History)
0 users

See Also:
Source RPM: drakxtools-curses-16.26.12-1.mga4
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Gabriel Gazzan 2015-06-16 23:54:58 CEST 
The "drakdisk" program crashed. Drakbug-16.26.12 caught it.

Creating a RAID 0 device from 2 hard drives.

current_hd called but $current_kind is not an hd (raid) at /usr/lib/libDrakX/diskdrake/hd_gtk.pm line 406.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm:295
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1502
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:749
ugtk3::main() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:132
diskdrake::hd_gtk::main() called from /usr/libexec/drakdisk:93

Theme name: oxygen-gtk
Kernel version = 3.14.32-desktop-1.mga4
Distribution=Mageia release 4 (Official) for x86_64
CPU=Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
Comment 1 Samuel Verschelde 2015-06-17 11:06:23 CEST 
Thanks for reporting. Assigning to maintainer.

Assignee: bugsquad => thierry.vignaud

Comment 2 Thierry Vignaud 2015-06-17 12:52:05 CEST 
Dup

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Summary: drakdisk crashed => drakdisk crashed (current_hd called but $current_kind is not an hd (raid) at /usr/lib/libDrakX/diskdrake/hd_gtk.pm line 406)
Note You need to log in before you can comment on or make changes to this bug.