Karmic: splash is added to recovery mode kernel with update-grub

Bug #412093 reported by dentaku65
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

In karmic I've noted that splash entry in the grub.cfg is present in the line of recovery mode:

menuentry "Ubuntu, Linux 2.6.31-5-generic (recovery mode)" {
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set b9b35c5e-8eee-408e-a72a-9c0505620ad0
 linux /boot/vmlinuz-2.6.31-5-generic root=UUID=b9b35c5e-8eee-408e-a72a-9c0505620ad0 ro single splash #GRUB_DISABLE_LINUX
_UUID=true quiet
 initrd /boot/initrd.img-2.6.31-5-generic
}

This causing freeze on recovery menu (not possible to use arrow keys, hard reboot needed); removing splash from grub editing command line at boot then booting with ctrl-x recovery it works.

I follow this guide to modify the entry in grub.cfg
https://wiki.ubuntu.com/Grub2#User-defined%20Entries
but when I load the command after the changes
sudo update-grub
the splash line on recovery kernel is put it back.

Revision history for this message
xtknight (xt-knight) wrote :

I haven't seen this in my grub.cfg.

Revision history for this message
Colin Watson (cjwatson) wrote :

Did you perhaps upgrade from an early version of grub2? This is probably caused by an incorrect /etc/default/grub file. The current default looks like this:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

... but if instead you had:

  GRUB_CMDLINE_LINUX="quiet splash"

... then you'd find those options added to recovery mode as well as normal mode.

Changed in grub2 (Ubuntu):
status: New → Incomplete
Revision history for this message
dentaku65 (dentaku65) wrote :

No installed from scratch Alpha 3.
I just used startupmanager adding 10 seconds before the boot instead 5 seconds.
But when the new grub2 update 3 days ago has been proposed I've choose the maintainer configuration.

Revision history for this message
dentaku65 (dentaku65) wrote :

this is my /etc/default/grub

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=3
GRUB_TIMEOUT=6
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
GRUB_CMDLINE_LINUX="splash #GRUB_DISABLE_LINUX_UUID=true quiet"

Revision history for this message
Colin Watson (cjwatson) wrote :

This last line is badly garbled:

  GRUB_CMDLINE_LINUX="splash #GRUB_DISABLE_LINUX_UUID=true quiet"

The stock file in the package says:

  #GRUB_DISABLE_LINUX_UUID=true

You should replace your last line with the stock one to fix this bug.

Something clearly went wrong when you chose to replace your existing configuration with the maintainer configuration. Did you use an editor to do this, or did you select a choice in a dialog?

Revision history for this message
Colin Watson (cjwatson) wrote :

Oh, and did you use startupmanager after the upgrade too, or only before?

Revision history for this message
dentaku65 (dentaku65) wrote :

I select the maintainer one as choice in the dialog.
I used startupmanager before and after.

ok, changhing the last line as indicated by Colin fix the problem with
sudo update-grub

Revision history for this message
Joshua (joshudson) wrote :

I can confirm this does in fact happen and believe this fixed in lucid.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.