The "drakdisk" program crashed. Drakbug-16.26.12 caught it. Clicked on the "unused" space in the bogus volume group PVS. # vgs Logging initialised at Tue Oct 21 13:25:54 2014 Set umask from 0022 to 0077 vgs Finding all volume groups vgs Finding volume group "bk" vgs Finding volume group "91" vgs Finding volume group "a8" vgs VG #PV #LV #SN Attr VSize VFree vgs 91 1 1 0 wz--n- 128.00g 31.50g vgs a8 8 1 0 wz--n- 378.20g 6.55g vgs bk 1 7 0 wz--n- 69.54g 0 vgs Wiping internal VG cache None of the above volume groups are shown by diskdrake, just the non-existent volume group PVS. I want to increase the ext4 filesystem in the vg a8, but can't do that now with diskdrake. I have used it in the past to create, and increase the space used by a filesystem on a vg, so know how it used to work. Illegal division by zero at /usr/lib/libDrakX/diskdrake/interactive.pm line 1409. 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.22-desktop-1.mga4 Distribution=Mageia release 4 (Official) for i586 CPU=Intel(R) Celeron(R) CPU 2.40GHz
Assignee: bugsquad => thierry.vignaud
Summary: drakdisk crashed => drakdisk crashed (llegal division by zero at diskdrake/interactive.pm line 1409)
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD