Not really; the error not showing up is because the firmware doesn't
report an error, but even if it did we can't necessarily tell the user
anything from it anyway (it might not be breaking because of Boot Order
Lock).
Fallback is a "new" feature to fix other systems that don't remember how
to boo
Thank you Mathieu, your suspicion was correct: After disabling that
setting, the message on boot is gone, the latest versions of the
packages work and I now see an "ubuntu" entry next to the NVMe entry in
the UEFI boot device menu.
This resolves my immediate issue. I guess the actual problem is th
The packages themselves are not buggy. This appears to be an issue
caused by firmware doing exactly what it is told and designed to do.
I didn't notice that earlier, but there's a "Boot Order Lock" option in
Lenovo's firmware, and it is set to Enabled in the screenshots you
provided.
Automated bo
When I first encountered the problem, I first tried to let boot-repair
(run from a live system) repair my Grub installation, since I'm not too
familiar with the boot process on UEFI. It failed multiple times, even
when I disabled Secure Boot and when I enabled the CSM and tried to
install grub-pc.
I really don't think you're affected by the same issue as the other bug.
I see there's a BootOrder set (at least, once booted), and there's an
ubuntu entry that looks correct, but that does depend on what you're
supposed to be booting to. The screenshot you include says the system
should be bootin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750351
Title:
(Thin
