Bug 1745355 - Something has gone seriously wrong: import_mok_state() failed
Summary: Something has gone seriously wrong: import_mok_state() failed
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lorax
Version: 30
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-25 16:30 UTC by Lonni J Friedman
Modified: 2020-05-01 15:47 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-01 15:47:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 15522 0 None None None 2019-08-25 16:30:18 UTC

Description Lonni J Friedman 2019-08-25 16:30:18 UTC
Description of problem:
Attempting to install Fedora 30 on an old Macbook Air (7.1), and
as soon as it tries to boot from the USB stick, it fails, printing the
following errors:
######
Failed to start MokManager: Not Found
Something has gone seriously wrong: import_mok_state() failed
######

after which the laptop powers off on its own.  This is before any sort
of GRUB menu or anything interactive appears.  Its literally this bug:
https://bugs.centos.org/view.php?id=15522

But I'm puzzled how the Fedora 30 grub bits could be broken in this fashion?

Version-Release number of selected component (if applicable):


How reproducible:
100% of the time

Steps to Reproduce:
1. Attempt to boot from the Fedora 30 install image
2. Error msg appears before anything else happens


Actual results:
Failure to install OS

Expected results:
Installer runs to completion without failures/errors

Comment 1 Peter Jones 2020-01-27 16:43:38 UTC
I think this means we should have mockmanager in /EFI/BOOT/ on the USB stick and don't.  You can copy mmx64.efi from the package into that directory from the package to work around this.

Comment 2 Brian Lane 2020-01-27 23:43:12 UTC
As far as I can tell it is already in /EFI/BOOT
I see mmx64.efi in /EFI/BOOT of the iso and at /EFI/BOOT of /images/macboot.img

If someone with the hardware can figure out exactly what needs to be changed please open a PR with lorax: https://github.com/weldr/lorax

Comment 3 Lonni J Friedman 2020-01-27 23:47:23 UTC
I have the hardware, but no clue what needs to be changed to fix this.  That's why I opened this bug originally.

Comment 4 Ben Cotton 2020-04-30 20:30:06 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.


Note You need to log in before you can comment on or make changes to this bug.