[Bug 462888] Re: grub2 menu stays until I press enter

Marcus Tomlinson marcus.tomlinson at canonical.com
Thu Mar 5 12:37:35 UTC 2020


This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.

** Changed in: grub2 (Ubuntu)
       Status: Confirmed => Incomplete

-- 
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/462888

Title:
  grub2 menu stays until I press enter

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: grub2

  Ubuntu 9.10 Karmic Koala beta

  grub2~1.97-beta4-1ubuntu3

  grub2 menu stays until I press enter.

  grubenv reads: recordfail=1

  My understanding is, that it should only read "1" if there was a boot
  problem

  or a "suspend / hibernate" problem.

  The OS does put PC into "suspend" mode, & I can awaken it from there.

  However, I have set "Never" mode for both PC & Monitor (in Power
  Management),

  so it should not put the PC into "suspend" in the first place.

  But Grub2 apparently is told that the PC failed, because if I manually
  put recordfail=0

  it always changes back to recordfail=1, & thus the grub2 menu appears
  indefinitely,

  until I press enter.

  I have devised a work-around that fixes the symptom but not the actual
  bug:

  by adding the following to the bottom of the /etc/grub.d/40_custom
  script:

  fi
  if [ ${recordfail} = 1 ]; then
    set timeout=3
  else
    set timeout=0
  fi
  # end

  in this way if there was a problem with booting or suspend / hibernate

  one has whatever timeout one adds to this script,

  & if grubenv were set with recordfail=0 it would boot without delay.

  As I wrote, it does not fix the actual bug, & perhaps it really is two
  bugs.

  one in ACPI managing, & the other in not resetting grub2 recordfail.

  as to "Required input missing": I was unable to use the "Record a
  problem..."

  program, it refused to start, so I used: sudo ubuntu-bug grub2, to
  report.

  I could not find this exact bug described, so a new bug report may
  help.

  I have attached grub.cfg, which of course shows the altered 40_custom.

  BavarianPH,

  Ubuntu forever!

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: 3bb3e9fd3b939fdb7916d5535ab9761d
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Wed Oct 28 14:15:58 2009
  DistroRelease: Ubuntu 9.10
  Package: grub2 1.97~beta4-1ubuntu3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
  SourcePackage: grub2
  Uname: Linux 2.6.31-14-generic-pae i686

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



More information about the foundations-bugs mailing list