[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
** Tags removed: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
This is probably fixed in the disco dailies (and in disco beta), which now include /EFI/BOOT/mmx64.efi on the image - a recent change. Is this problem reproducible for you with the current image? If it is, we'll need to reassign it somewhere other than ubiquity. ** Changed in: ubiquity (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
** Tags added: disco rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
\EFI\BOOT\mmx64.efi should be on all the images; we should investigate this in case it was somehow dropped. The issue seems to be that we immediately go apply the changes when people configure Secure Boot in the installer, but this requires MokManager to run at the very next boot -- if it's not available anywhere, we should fail more gracefully than we currently do though. Still, MokManager is supposed to be on the images. ** Changed in: ubiquity (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
The Lenovo setup interface has put Secure Boot and UEFI/Legacy Boot on different pages even though the two prompts interact with each other. Turning Secure Boot off on one screen will then let you switch to Legacy Boot, and then the memory stick will boot again. More tomorrow. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
Hmm, the 'current' symlink still points to the march 5 image: http://cdimage.ubuntu.com/daily-live/current/ Is there enough chance that a newer, not-current, image would let me boot again? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
I can't boot arch on a memory stick, either, but there's no error message. It just returns to the uefi boot menu: 1f3541cbaa93ac64c9bf474ec7927d8274654ea01de046a75f39fdf972ad2a0d archlinux-2019.03.01-x86_64.iso Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
