[Bug 502138] Re: grub-pc keystatus check

TJ ubuntu at iam.tj
Tue May 10 06:46:20 UTC 2016

Setting this to Fix Released since 30_osprober was modified since 2010
and this no longer affects any Ubuntu release.

An issue that may be confused with this is bug 425979 "[UEFI boot only]
Holding shift fails to display grub2 menu"

** 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.

  grub-pc keystatus check

Status in grub2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: grub2

  I don't know if this is a bug or by intentional design.

  My question relates to the availability to use the SHIFT key to
  display the Grub 2 menu during boot.

  The keystatus check is nested within 30_os-prober conditionals. Unless
  30_os-prober is executed and these conditions are met it is not
  incorporated into grub.cfg.

  Additionally, it seems that the keystatus check turns control back
  over to GRUB_TIMEOUT if invoked. Thus, if GRUB_TIMEOUT=0 the keystatus
  check may note the depressed SHIFT key but the default menu will
  automatically boot without stopping the boot sequence to display the

  If it is designed merely to interrupt the GRUB_HIDDEN_TIMEOUT and then
  immediately revert to the GRUB_TIMEOUT, I would suggest that the user
  wants to see the menu when the SHIFT key is pressed, even if the
  timeout is set to 0.

  Workaround: I can incorporate the keystatus check by putting it into
  40_custom and can then display the menu regardless of the settings.

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Jan  1 13:48:29 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia
  Package: grub-pc 1.97~beta4-1ubuntu4.1
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: grub2
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list