UEFI/Secureboot - "Failed to start MokManager" error when trying to install 3rd party drivers during install, leading to unbootable device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Critical
|
Mathieu Trudel-Lapierre | ||
Eoan |
Fix Released
|
Critical
|
Mathieu Trudel-Lapierre |
Bug Description
Image: http://
Device: Dell XPS 13 7390 (201908-27305)
Note:
- TPM2 is disabled (because of lp:1845454)
- Secure Boot is enabled
Install Ubuntu 19.10.
Check the box "Install third party drivers". You'll have to input a password used by Secure Boot at the next reboot.
Complete the installation and restart the device.
Expected result:
The device reboots in the MOK Management screen where you can enroll the new MOK. Then the boot process continues and you can log in Ubuntu.
Actual result:
The following error is shown for a few seconds, then the device turns off:
Failed to open \EFI\ubuntu\
Failed to load image \EFI\ubuntu\
Failed to start MokManager: Not Found
Something has gone seriously wrong: import_mok_state() failed: Not Found
tags: | added: amd64 ce-qa-concern iso-testing rls-ee-incoming |
summary: |
- Dell XPS 13 7390 - "Failed to start MokManager" error when trying to - install 3rd party driving during install, leading to unbootable device + UEFI/Secureboot - "Failed to start MokManager" error when trying to + install 3rd party drivers during install, leading to unbootable device |
tags: | removed: rls-ee-incoming |
Changed in mokutil (Ubuntu Eoan): | |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
affects: | mokutil (Ubuntu Eoan) → grub2 (Ubuntu Eoan) |
Changed in grub2 (Ubuntu Eoan): | |
status: | Confirmed → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1845466
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.