Bug 18809

Summary:	draklive-install crashed (update-grub2 failed)
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, thierry.vignaud, zen25000
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	draklive-install-2.7-1.mga6, grub2	CVE:
Status comment:

Description Ben McMonagle 2016-06-28 09:51:43 CEST

The "draklive-install" program crashed. Drakbug-17.46 caught it.

attempting CSM x86-64  Live Gnome install to non-UEFI GPT HDD, 
"Use Existing Partitions" option 

update-grub2 failed:  at /usr/lib/libDrakX/any.pm line 613.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/libDrakX/any.pm:613
any::setupBootloader__grub2() called from /usr/lib/libDrakX/any.pm:228
any::setupBootloader() called from /usr/lib/libDrakX/any.pm:240
any::setupBootloaderUntilInstalled() called from /usr/sbin/draklive-install:332
main::setup_bootloader() called from /usr/sbin/draklive-install:70
main::install_live() called from /usr/sbin/draklive-install:42

Theme name: Adwaita
Kernel version = 4.6.3-desktop-1.mga6
Distribution=Mageia release 6 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz


My installation test HDD is GPT type, previously grub2 has been installed without issue :(

Comment 1 Thierry Vignaud 2016-06-28 11:20:36 CEST

Could you try running update-grub2 manually as root in a terminal when the crash occurs?
So that we can get an actual error message

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud, zen25000
Summary: draklive-install crashed => draklive-install crashed (update-grub2 failed)

Thierry Vignaud 2016-06-28 11:22:49 CEST

Source RPM: draklive-install-2.7-1.mga6 => draklive-install-2.7-1.mga6, grub2

Comment 2 Ben McMonagle 2016-06-29 10:59:14 CEST

I have attempted 3 installs tonight. (and every one was a success)

Due to the +15min bootoader install for me, thats + 2 hours.

I would suggest leavng this as unconfirmed, I will append it if/when happens again

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 3 Thierry Vignaud 2016-06-29 11:16:33 CEST

Well it did happen once so that would still be a valid bug
Sadly we don't have logs about the original one...

Comment 4 Marja Van Waes 2017-01-07 11:36:49 CET

Assuming this is the same issue as bug 18927, which was filed by the same reporter and contains more information.

Closing this bug as duplicate of that one

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

Status: UNCONFIRMED => RESOLVED
CC: (none) => marja11
Resolution: (none) => DUPLICATE