> I suspect this has something to do with the update to shim-signed 1.33.1~17.10.1
We know that some Acer systems have non-compliant UEFI firmware implementations, and do not honor boot options configured via efibootmgr from the OS. It sounds like this is the case for your system, and that as a result, your system is being booted via \EFI\BOOT\BOOTX64.EFI, which is indeed part of shim; and that this triggers fbx64.efi, the "fallback" behavior, to try to recover the contents of the Boot* variables based on the provided information in \EFI\*\BOOTX64.CSV (in this case, probably only \EFI\ubuntu\BOOTX64.CSV). But because the Acer firmware is broken, after fbx64.efi "successfully" repopulates the Boot* variables and reboots, the firmware again boots to fallback instead of to the correct boot entry. I don't think there is anything we can do to detect or fix this in Ubuntu. The primary bug here is that the Acer system is booting \EFI\BOOT\BOOTX64.EFI which it should never do (and which Ubuntu did not configure it to do). I think your change to boot "EFI File Boot 0" is (despite the poor boot option naming) the correct fix for your system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747889 Title: System not booting after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1747889/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
