[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Steve Langasek
steve.langasek at canonical.com
Tue Feb 5 06:08:52 UTC 2019
** Also affects: grub2 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Status: New => Triaged
** Changed in: grub2 (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: grub2 (Ubuntu Cosmic)
Importance: Undecided => High
--
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:
Fix Released
Status in grub2 source package in Bionic:
Triaged
Status in grub2 source package in Cosmic:
Triaged
Bug description:
[SRU Justification]
There is a behavior regression on non-EFI systems with the latest SRU of grub2 which causes unnecessary boot delays.
[Test case]
1. Install a system using BIOS mode with /boot on LVM.
2. Reboot and verify that the boot menu is shown for 30 seconds at boot.
3. Install grub* from -proposed.
4. Reboot and verify that the boot menu is not shown.
5. Install a system using UEFI mode with /boot on LVM.
6. Reboot and verify that the boot menu is shown for 30 second at boot.
7. Install grub* from -proposed.
8. Reboot and verify that the boot menu is still shown.
[Regression potential]
The test case is sufficient to verify all possible paths work correctly after the SRU.
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