One difference I noticed when running `efibootmgr` in another laptop, also plucky, is that the firmware updater entry seems to have an extra parameter there:
Boot0002* Linux-Firmware-Updater HD(1,GPT,d8bfcac5-daa4-4e87-a79a-a1ba61b879da,0x800,0x219800)/File(\EFI\ubuntu\shimx64.efi) File(.\fwupdx64.efi) Whereas on my machine where it's not working, that extra File() parameter is not there: Boot0001* Linux-Firmware-Updater HD(1,GPT,0fa5e368-f741-4510-a481-fac2e4ba4e05,0x800,0x219800)/File(\EFI\ubuntu\shimx64.efi) efibootmgr and fwupd* packages are at the same version, so I'm not sure what's going on. The system with the extra File() parameter is older, and I don't think it received any recent firmware updates, so maybe that uefi entry is old, created by a previous version of these packages? That laptop was reinstalled a few times in its life, and I *think* it was upgraded from noble or oracular recently, so maybe that entry came from when it was running those systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111199 Title: fwupd is incompatible with secure boot (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2111199/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
