If we don't have writable grubenv and we're on EFI, always show the menu
authorSteve Langasek <steve.langasek@ubuntu.com>
Tue, 30 Oct 2018 22:04:16 +0000 (15:04 -0700)
committerFelix Zielcke <fzielcke@z-51.de>
Wed, 11 Jun 2025 15:42:34 +0000 (17:42 +0200)
commit602b0d113f9ded73dca5cc1eeec41bbf85371568
treedd3793e35b4ec4e8d3467fae8d4644b205157c78
parent7d2ebd86df0ca1d7c25d8025ad3eb6cc159473ce
If we don't have writable grubenv and we're on EFI, always show the menu

If we don't have writable grubenv, recordfail doesn't work, which means our
quickboot behavior - with a timeout of 0 - leaves the user without a
reliable way to access the boot menu if they're on UEFI, because unlike
BIOS, UEFI does not support checking the state of modifier keys (i.e.
holding down shift at boot is not detectable).

Handle this corner case by always using a non-zero timeout on EFI when
save_env doesn't work.

Reuse GRUB_RECORDFAIL_TIMEOUT to avoid introducing another variable.

Signed-off-by: Steve Langasek <steve.langasek@canonical.com>
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1800722
Last-Update: 2019-06-24

Patch-Name: quick-boot-lvm.patch

Gbp-Pq: Name quick-boot-lvm.patch
util/grub.d/00_header.in