Bug 19998 - drakboot crashed (update-grub2 failed: at /usr/lib/libDrakX/bootloader.pm line 1814.)
Summary: drakboot crashed (update-grub2 failed: at /usr/lib/libDrakX/bootloader.pm li...
Status: RESOLVED DUPLICATE of bug 19997
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-21 06:29 CET by Shadows
Modified: 2018-10-07 17:00 CEST (History)
3 users (show)

See Also:
Source RPM: drakxtools-16.105.1-1.mga5
CVE:
Status comment:

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

Description Shadows 2016-12-21 06:29:47 CET 
The "drakboot" program crashed. Drakbug-16.105.1 caught it.

I had all other programs closed.  All I was doing was updating from GRUB legacy to GRUB2.

update-grub2 failed:  at /usr/lib/libDrakX/bootloader.pm line 1814.
	...propagated at /usr/lib/libDrakX/any.pm line 268.
	...propagated at /usr/libexec/drakboot line 64.
Perl's trace:
drakbug::bug_handler() called from /usr/libexec/drakboot:64

Theme name: oxygen-gtk
Kernel version = 4.4.30-desktop-2.mga5
Distribution=Mageia release 5 (Official) for x86_64
CPU=AMD E-300 APU with Radeon(tm) HD Graphics
Comment 1 Marja Van Waes 2016-12-21 06:57:58 CET 
OK, so you retried and it crashed at another line :-/

I was about to close it as duplicate, but am not sure it's a dup, so will leave it open.

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

Status: NEW => RESOLVED
CC: (none) => marja11, zen25000
Resolution: (none) => DUPLICATE
Assignee: bugsquad => mageiatools
Summary: drakboot crashed => drakboot crashed (update-grub2 failed: at /usr/lib/libDrakX/bootloader.pm line 1814.)

Comment 2 Marja Van Waes 2016-12-21 06:59:25 CET 
Oops

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

Comment 3 Shadows 2016-12-21 20:02:46 CET 
Yeah.  I retried it w/o any other applications open this time hoping that *maybe* it would do the trick and that it'd run through if there was nothing else interfering.

Clearly that didn't happen. :(

I'm not going to say that it's NOT a dup, but if it is it's not an exact dup.

(In reply to Marja van Waes from comment #1)
> OK, so you retried and it crashed at another line :-/
> 
> I was about to close it as duplicate, but am not sure it's a dup, so will
> leave it open.
> 
> *** This bug has been marked as a duplicate of bug 19997 ***
Shadows 2016-12-21 20:03:17 CET

CC: (none) => hvarenah

Comment 4 Marja Van Waes 2018-07-12 12:05:26 CEST 
Hi Shadows,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

If you didn't reset your password after february 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report.
Comment 5 Marja Van Waes 2018-10-07 17:00:03 CEST 
I guess this bug counted as a duplicate of bug 19997, after all.

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

Resolution: (none) => DUPLICATE
Status: REOPENED => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.