[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Steve Langasek
steve.langasek at canonical.com
Mon Feb 4 00:06:14 UTC 2019
Also,
> using EFI+btrfs boot volume. No LVM used, just GPT on NVMe.
Yes, this change was introduced to address the problem as seen on LVM-
backed /boot/grub, but that is certainly not the only configuration for
which GRUB has read support but lacks write support. The fix is generic
to all such filesystems that are read-only in GRUB, and that is by
design.
--
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:
Won't Fix
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