Public bug reported: After installing the latest updates for Ubuntu 17.10, my computer (Acer Aspire V3-372) was no longer able to boot. It got stuck in a loop, displaying the following error message for a few milliseconds, then restarting again:
System BootOrder not found. Initializing defaults. Creating boot entry "BootXXXX" with label "ubuntu" for file "\EFI\ubuntu\shimx64.efi" I suspect this has something to do with the update to shim-signed 1.33.1~17.10.1 as "Failure to boot or validate validly signed EFI binaries" is listed as a potential regression on https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1708245/+editstatus There was also a very similar bug reported for Fedora 27: https://bugzilla.redhat.com/show_bug.cgi?id=1512410 Selecting any (new) UEFI files as trusted did not solve the issue, neither did disabling secure boot or resetting the secure boot option in BIOS to factory default and it's still not working after adding EFI/ubuntu/shimx64.efi to trusted files again. The workaround I've found for now, is selecting "EFI File Boot 0" (which is the previously added trusted file) as primary boot device. But that's just a workaround, I think I should be able to just boot from my SSD as before. ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Package changed: grub2 (Ubuntu) => shim-signed (Ubuntu) -- 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
