update-grub doesn't add recovery anymore

Bug #73906 reported by Nafallo Bjälevik
22
Affects Status Importance Assigned to Milestone
grub (Ubuntu)
Fix Released
High
Colin Watson

Bug Description

After the latest update of grub (and update-grub) it does not add entries for the recovery options anymore.

Related branches

Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

Hobbsee confirmed on IRC

Changed in grub:
importance: Undecided → High
status: Unconfirmed → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

The problem is that "set -e" is used, which exits/returns on errors.
There's a mandatory argument missing for "write_kernel_entry" in two places.

The attached patch fixes this, but I'm not sure if it's the correct argument that gets passed here ("$do_lockold") or if it should be empty/"false"/whatever.

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

grub (0.97-20ubuntu1) feisty; urgency=low

  * Resynchronise with Debian. Remaining changes:
    - provide linux-boot-loader virtual package
    - compile with gcc-4.0
    - use -fno-strict-aliasing
    - quiet boot and usplash support
    - disabled patch to set splash
    - store version of grub in /boot/grub/installed-version
    - in update-grub use this file to determine whether the quiet option
      is supported
    - transition root option to mounting by UUID
    - fix bashisms in update-grub
    - rename "single-user" mode to "recovery" mode
    - detect installation onto removable devices, and adjust root device
    - don't override UUID= or LABEL= from /etc/fstab, leave it to the
      initramfs to do the right thing
    - kdump option detection
    - drop "any-" from architecture names in debian/control
  * update-grub: Remember to pass lockold arguments to write_kernel_entry
    (LP: #73906).

 -- Colin Watson <email address hidden> Wed, 20 Dec 2006 15:05:21 +0000

Changed in grub:
assignee: nobody → kamion
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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