Bug 11750 - drakboot crashed ((expand_symlinks: swap boot gfxmenu is relative))
Summary: drakboot crashed ((expand_symlinks: swap boot gfxmenu is relative))
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-11-25 11:44 CET by Piotr
Modified: 2015-03-31 02:55 CEST (History)
1 user (show)

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

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

Description Piotr 2013-11-25 11:44:20 CET 
The "drakboot" program crashed. Drakbug-15.73.1 caught it.

zmiana dysku boot

expand_symlinks: swap/boot/gfxmenu is relative
	...propagated at /usr/lib/libDrakX/any.pm line 263.
	...propagated at /usr/libexec/drakboot line 65.
Perl's trace:
standalone::bug_handler() called from /usr/libexec/drakboot:65

Theme name: oxygen-gtk
Kernel version = 3.12.1-desktop-1.mga4
Distribution=Mageia release 4 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Comment 1 Piotr 2013-11-25 11:45:23 CET 
 moving boot on second disk
Comment 2 Manuel Hiebel 2013-11-25 23:58:52 CET 
same bug on mga2 https://bugs.mageia.org/show_bug.cgi?id=6966 was closed as fixed

Assignee: bugsquad => thierry.vignaud

Manuel Hiebel 2013-11-25 23:59:17 CET

Summary: drakboot crashed => drakboot crashed ((expand_symlinks: swap boot gfxmenu is relative))

Comment 3 Thierry Vignaud 2013-11-26 10:52:28 CET 
What did you do exactly so that it stoped working?
Can you attach (not paste) your /etc/fstab (before & after your changes) as well as your /boot/grub/menu.lst and your /boot/grub/devices.map ?

Keywords: (none) => NEEDINFO

Comment 4 Nic Baxter 2015-03-31 02:55:14 CEST 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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