[Bug 669481] Re: Timeout should not be -1 if $recordfail

Wed May 30 11:15:24 UTC 2012

This bug was fixed in the package grub2 - 1.99-22ubuntu1

---------------
grub2 (1.99-22ubuntu1) quantal; urgency=low

  [ Colin Watson ]
  * Resynchronise with Debian.  Remaining changes:
    - Adjust for default Ubuntu boot options ("quiet splash").
    - Default to hiding the menu; holding down Shift at boot will show it.
    - Set a monochromatic theme and an appropriate background for Ubuntu.
    - Apply Ubuntu GRUB Legacy changes to legacy update-grub script.
    - Fix backslash-escaping in merge_debconf_into_conf.
    - Remove "GNU/Linux" from default distributor string.
    - Add crashkernel option.
    - Bypass menu unless other OSes are installed or Shift is pressed.
    - Allow Shift to interrupt 'sleep --interruptible'.
    - Reduce visual clutter in normal mode.
    - Remove verbose messages printed before reading configuration.
    - Suppress kernel/initrd progress messages, except in recovery mode.
    - Show the boot menu if the previous boot failed.
    - Don't generate device.map during grub-install or grub-mkconfig.
    - Adjust upgrade version checks for Ubuntu.
    - Suppress "GRUB loading" message unless Shift is held down.
    - Adjust versions of grub-doc and grub-legacy-doc conflicts.
    - Fix LVM/RAID probing in the absence of /boot/grub/device.map.
    - Look for .mo files in /usr/share/locale-langpack first.
    - Build-depend on qemu-kvm rather than qemu-system for grub-pc tests.
    - Check hardware support before using gfxpayload=keep.
    - Put second and subsequent Linux menu entries in a submenu.
    - Preferred resolution detection for VBE.
    - Set vt.handoff=7 for smooth handoff to kernel graphical mode.
    - Update default/grub.md5sum to include maverick's default md5sum.
    - In recovery mode, add nomodeset to the Linux kernel arguments, and
      remove the 'set gfxpayload=keep' command.
    - Skip Windows os-prober entries on Wubi systems, and suppress the menu
      by default if those are the only other-OS entries.
    - Handle probing striped DM-RAID devices.
    - Replace 'single' by 'recovery' when friendly-recovery is installed.
    - Use qemu -no-kvm in tests for now to work around LP #947597.
    - Disable cursor as early as possible in grub_main.
    - Don't crash on inaccessible loop device backing paths.
    - Backport several upstream EFI device discovery patches.

  [ Ben Howard ]
  * Parameterization of recordfail setting. This allows users to define the
    default time out of GRUB when recordfail has been set. The current
    setting causes hangs on headless and appliances where access to the
    console is limited or prohibited.  (LP: #669481)

grub2 (1.99-22) unstable; urgency=low

  [ Debconf translations ]
  * Khmer added (Khoem Sokhem)
  * Slovenian (Vanja Cvelbar).  Closes: #670616
  * Traditional Chinese (Vincent Chen).
  * Vietnamese (Hai Lang).
  * Marathi (Sampada Nakhare)
  * Finnish (Timo Jyrinki).  Closes: #673976
  * Latvian (Rūdolfs Mazurs).  Closes: #674697

  [ Colin Watson ]
  * Make apport hook compatible with Python 3.
  * Add upstream r3476 (fix memory leak in grub_disk_read_small) to
    4k_sectors.patch, otherwise the larger disk cache due to
    efi_disk_cache.patch can cause EFI systems to run out of memory.
 -- Colin Watson <cjwatson at ubuntu.com>   Wed, 30 May 2012 12:11:57 +0100

** Branch linked: lp:~ubuntu-core-dev/ubuntu/quantal/grub2/quantal

** Changed in: grub2 (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/669481

Title:
  Timeout should not be -1 if $recordfail

Status in “grub2” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: grub2

  My experience is that $recordfail is not always written successfully,
  which is by default tested in grub.cfg (through grub.d/00_header)

  This causes grub2 to set timeout=-1 which removes the timeout for
  bootup in these cases.

  On computers which have not been configured for "USB Legacy" in the
  BIOS but use USB keyboards, this looks as if grub has frozen - because
  the keyboard does not respond. The consequence is that the computer
  won't boot without either knowledge on how to configure BIOS (and
  what) or using a PS/2 keyboard (not always available or possible to
  plugin).

  My suggestion is that Ubuntu recognizes $recordfail but instead of
  disabling timeout (-1) it should be set to a relatively high value
  (such as 10 seconds). This will be enough to alert the user on what
  option is booting, and that the computer hasn't frozen, as well as
  enabling false/known failures to be ignored.

  Maybe a future addition to recognising $recordfail is to have a
  warning on the boot menu, but that is outside the scope of this
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: grub-pc 1.98+20100804-5ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
  Uname: Linux 2.6.35-22-generic-pae i686
  Architecture: i386
  Date: Mon Nov  1 15:33:30 2010
  InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/669481/+subscriptions