[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
m4t
1814403 at bugs.launchpad.net
Sun Feb 3 18:17:02 UTC 2019
I believe it had to do with the patch debian/patches/quick-boot-
lvm.patch as described here:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1800722
Here's what I wrote in a comment (#12) there a couple days ago:
Seeing a regression here on 18.10/amd64 with 2.02+dfsg1-5ubuntu8.1 using
EFI+btrfs boot volume. No LVM used, just GPT on NVMe.
Regardless of my settings in /etc/default/grub, the boot wait is now 30
seconds.
Relevant settings:
GRUB_HIDDEN_TIMEOUT=1
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=0
I've downgraded using the following commands:
apt install grub-common=2.02+dfsg1-5ubuntu8 grub-efi-amd64=2.02+dfsg1-5ubuntu8 grub-efi-amd64-bin=2.02+dfsg1-5ubuntu8 grub2-common=2.02+dfsg1-5ubuntu8
apt-mark hold grub2-common grub-efi-amd64
And it's returned the previous behavior.
--
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/1814403
Title:
Latest update causes 30 sec. menu delay timeout
Status in grub2 package in Ubuntu:
Confirmed
Bug description:
KDEneon LTS user edition 5.12, Release 18.04
grub-common 2.02-2ubuntu8.10 from Ubuntu updates
Since latest update near the end of Jan. 2019 (29th?), grub menu has
30 second delay every reboot as though recordfail is set. It did not
do this before the update.
After messing with grubenv and recordfails settings, I found this
paragraph in 00_header in 18.04 that is not in 16.04:
if lsefi; then
set timeout=30
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi
Note "timeout=30" which is the same as the recordfail timeout. As a
test, I edited /boot/grub/grub.cfg and changed the 30 to 17 and sure
enough, that's the source of the timeout.
Here's the paragraph from 00_header:
if lsefi; then set timeout=${GRUB_RECORDFAIL_TIMEOUT:-30}
if [ x\$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi
One odd thing is the 00_header file is from Jan 9th but this bug has
just appeared so it must be related to grub-common not the the header
file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions
More information about the foundations-bugs
mailing list