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

[Moritz Baumann]

@yogeshpathade: See my first post. You'll have to boot into a live
system, mount the root filesystem, chroot into it and replace the
versions of shim-signed and grub with the original versions. To do so,
purge the installed versions, look up the original versions of those
packages via "apt-cache policy [package]" and then install those via
"apt install [package]=[version]". Boot-repair will not work since it
will try to install the latest versions, which don't work on our
hardware.

@vorlon: Since this bug seems to affect multiple Thinkpad models, the
title and the priority of this bug should probably be changed.

-- 
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:
  Confirmed

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