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

[Moritz Baumann]

I've taken a bunch of photos (see attachments). Please tell me what
other screens you're interested in, I included the "Security" menu
overview.

Product information from lshw:
    product: 20HES0FA35 (LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470)
    vendor: LENOVO
    version: ThinkPad T470
    serial: [...]
    width: 64 bits
    capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
    configuration: administrator_password=enabled chassis=notebook family=ThinkPad T470 power-on_password=disabled sku=LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 uuid=[...]

This is what lshw says about my BIOS:
          description: BIOS
          vendor: LENOVO
          physical id: b
          version: N1QET69W (1.44 )
          date: 12/13/2017
          size: 128KiB
          capacity: 15MiB
          capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb biosbootspecification uefi


** Attachment added: "BIOS_SETTINGS.pdf"
   https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1747889/+attachment/5054116/+files/BIOS_SETTINGS.pdf

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