[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed

[Seth Arnold]

Thanks for fixing up the missing /EFI/BOOT/mmx64.efi.

With the disco beta image I was able to re-enable the secure boot
setting in my bios. I'll try to fiddle around with the installer and try
to spot if the 'cancel' button doesn't undo pending changes. (But I'm
not sure how to test that.)

Thanks

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

Title:
  Something has gone seriously wrong: import_mok_state0 failed

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  This may be related to bug 1798171.

  I booted my new Lenovo X1 carbon 6th generation from a memory stick
  using:

  $ ls -l disco-desktop-amd64.iso ; sha256sum ./disco-desktop-amd64.iso 
  -rw-rw-r-- 1 sarnold sarnold 2030043136 Mar  5 09:51 disco-desktop-amd64.iso
  2fe72e17a2dc575ee90bd7f932e345975f04546ebe2154870198153f80de5336  ./disco-desktop-amd64.iso

  I updated the BIOS using the Lenovo-supplied Windows BIOS update tools
  before booting Ubuntu.

  The live session worked fine for a few days.

  I started the installer, clicked boxes for turning on secure boot,
  typed in a secure boot password, and when I didn't see anything about
  ZFS in the disk partitioning page, I cancelled out of the installer.

  The next reboot into the memory stick gave these messages before
  turning off:

  Failed to open \EFI\BOOT\mmx64.efi - Not Found
  Failed to load image \EFI\BOOT\mmx64.efi: Not Found
  Failed to start MokManager: Not Found
  Something has gone seriously wrong: import_mok_state0 failed
  : Not Found

  
  I cannot boot into the Ubuntu live memory stick any more. These messages repeat then the system turns off again. Windows still boots, which is encouraging, but I don't know how to use Windows.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions