[Bug 1747889] Re: (Acer Aspire V3-372) System not booting after update

[Mathieu Trudel-Lapierre]

That's great, those are the screens I was interested in.

Looks like this may actually be a different bug. Could you please go
ahead and file a separate bug report for your system (use 'ubuntu-bug
shim')?

Is this an install of 16.04 like I think it is, and if so, is there any
way you could boot to an Ubuntu session (such as using a live CD / USB)
and get the output of 'sudo efibootmgr -v' to include on the bug?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1747889

Title:
  (Acer Aspire V3-372) System not booting after update

Status in shim-signed package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1747889/+subscriptions