[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout

[Steve Langasek]

It is expected behavior that, after this SRU, some systems which are
configured in such a way that /boot/grub is not writable by grub will
take longer to boot.  This is a boot speed regression, but it is not a
functional regression; no systems should be failing to boot as a result
of this change.

The change is deliberate and necessary because without it, it is
impossible on a UEFI system to reliably access the boot menu.  That
means that if you ever had a kernel that fails to boot, you will be
stuck with a non-bootable system and be unable to recover it from the
grub menu (by booting the previous, working kernel).

So I believe this bug is 'wontfix'.

** Changed in: grub2 (Ubuntu)
       Status: Confirmed => Won't Fix

-- 
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