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)
committerMate Kukri <mate.kukri@canonical.com>
Tue, 10 Feb 2026 11:27:19 +0000 (11:27 +0000)
commitcadd9ec63bd44aead34d2489e4a878a1a0d3bca6
tree13ba4d663f6a8f114695a2f9974e95588f4e5c81
parent0659ed0dc634741e7646bb93c2c3c1e8ac36c30b
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