flicker-free boot gets interrupted by GRUB menu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I have a Dell XPS 9300 running Ubuntu 20.04. I have installed Ubuntu using full disk encryption as documented at https:/
When I power on my laptop, I get the Dell boot logo and GRUB prompt asking me to enter the hard drive decrypt password. After entering the password, after the decrypt completes, the screen displays a GRUB boot options menu. After I hit enter, the Dell boot logo and the spinning Ubuntu logo are displayed again continue until the login screen is displayed.
Ideally, the GRUB menu should not be displayed, so that the whole boot process is flicker free. The menu is (afaict) being shown by the following code in /boot/grub/grub.cfg :
---
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_
set timeout_
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
if [ $grub_platform = efi ]; then
set timeout=30
if [ x$feature_
set timeout_style=menu
fi
fi
---
The last if condition appears to force displaying the menu if the boot mode is EFI. I do not understand why this is necessary.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: grub-common 2.04-1ubuntu26
ProcVersionSign
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Mon May 11 18:52:55 2020
InstallationDate: Installed on 2020-04-23 (18 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for your bug report. Could you maybe make a video from the system boot? The password should be asked by plymouth nor grub but it's difficult to say if that's what is happening from the bug description
Could you also add your 'journalctl -b 0' log from a boot having the issue? do you have other another OS installed?