Bug 4290 - drakboot crashed (mkinitrd failed) after edited another linux's entry
Summary: drakboot crashed (mkinitrd failed) after edited another linux's entry
Status: RESOLVED DUPLICATE of bug 4285
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-26 20:31 CET by Arthur Poór
Modified: 2012-01-27 00:49 CET (History)
0 users

See Also:
Source RPM: drakxtools-13.58-1.mga1
CVE:
Status comment:

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

Description Arthur Poór 2012-01-26 20:31:54 CET 
The "drakboot" program crashed. Drakbug-13.58 caught it.

Overview:
I tried to modify an entry that I added via edit the menu.lst file by hand before.

----------------------------

Steps to reproduce:
1) change the kernel and/or initram version string by write directly in the textbox, as opposed to browse the file.

----------------------------

Additional information:
The entry was:
title CentOS
root (hd0,5)
        kernel /vmlinuz-2.6.32-220.2.1.el6.x86_64 ro root=/dev/mapper/CentOS-centos_root rd_LVM_LV=CentOS/centos_root rd_NO_LUKS LANG=en_US.UTF-8  KEYBOARDTYPE=pc KEYTABLE=hu rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto rd_NO_DM nouveau.modeset=0 rdblacklist=nouveau
        initrd /initramfs-2.6.32-220.2.1.el6.x86_64.img

----------------------------

Backtrace was:
mkinitrd failed:
(mkinitrd -f (hd0,5)/initramfs-2.6.32-220.4.1.el6.x86_64.img 2.6.32-220.4.1.el6.x86_64) at /usr/lib/libDrakX/bootloader.pm line 124.
	...propagated at /usr/sbin/drakboot line 65.
standalone::bug_handler() called from /usr/sbin/drakboot:65

Kernel version = 2.6.38.8-desktop-9.mga
Distribution=Mageia release 1 (Official) for x86_64
CPU=Intel(R) Core(TM)2 Duo CPU     T5450  @ 1.66GHz
Comment 1 Manuel Hiebel 2012-01-27 00:49:46 CET 
same backtrave

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

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