Bug 25734 - drakboot crashed
Summary: drakboot crashed
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-24 09:08 CET by Vincent beuselinck
Modified: 2019-12-26 18:58 CET (History)
1 user (show)

See Also:
Source RPM: drakxtools-18.21-1.mga7
CVE:
Status comment:

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

Description Vincent beuselinck 2019-11-24 09:08:24 CET 
The "drakboot" program crashed. Drakbug-18.21 caught it.

MC --> Configurer le démarrage du système --> suivant

update-grub2 failed: /usr/sbin/grub2-probe : erreur : impossible d'obtenir le chemin canonique de « overlay ».
	...propagated at /usr/libexec/drakboot line 49.
Perl's trace:
drakbug::bug_handler() called from /usr/libexec/drakboot:49

Theme name: Adwaita
Kernel version = 5.1.14-desktop-1.mga7
Distribution=Mageia release 7 (Official) for x86_64
CPU=Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
Comment 1 Lewis Smith 2019-11-24 16:18:25 CET 
Does this happen consistently, or just once?
If repeatedly, can you please start drakboot in English, with the following command (as root):
 # LC_ALL=C drakboot 2>&1 | tee bug25734.txt
reproduce the crash, and then attach bug25734.txt to this bug report?
-----
There are several superficially similar bugs, all Mageia 6: 21817, 22395, 23298.
They all contain, like this bug:
"Perl's trace:
drakbug::bug_handler() called from /usr/libexec/drakboot:49"
but the exact reason is different each time, so one canot say they are duplicates.

Assigning to mageiatools group.

CC: (none) => lewyssmith
Assignee: bugsquad => mageiatools

Comment 2 Vincent beuselinck 2019-12-26 18:58:22 CET 
After an update (kernel 5.4.2 now) I can't reproduce this bug.

I propose to close this one

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