grub-pc keystatus check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
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 menu.
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)
NonfreeKernelMo
Package: grub-pc 1.97~beta4-
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: grub2
Uname: Linux 2.6.31-14-generic x86_64
Changed in grub2 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
If I'm reading you correctly, then I'm unable to reproduce this. That is, if you're saying that having the keystatus check in grub.cfg depends on another OS being found by os-prober, it's not what I'm seeing in my setup: here, os-prober *does* incorporate the keystatus check into grub.cfg despite Karmic being the only OS present. But do correct me if I'm reading you wrong.
There's another issue though, the keypress not getting picked up by grub despite it being present in the config: Bug #425979 (which is why I was curious about whether I could reproduce this one).