MOK enrollment is not adequately explained
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
New
|
Undecided
|
Unassigned | ||
ubiquity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The installer says:
"After installation completes, Ubuntu will assist you in configuring UEFI Secure Boot. ..."
In reality, the MOK management tool opens to a menu with four options and zero context:
1. Continue boot
2. Enroll MOK
3. Enroll key from disk
4. Enroll hash from disk
The user should not have to select 2 manually, but if they do, you should probably tell them about it.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 09:19:07 2024
InstallCmdLine: BOOT_IMAGE=
InstallationDate: Installed on 2024-04-16 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | ubuntu → ubiquity (Ubuntu) |
Marked as affecting subiquity, which is the core of the current installer in 24.04.
This is a valid bug against Ubuntu 22.04, but unlikely to be resolved because development of ubiquity is discontinued, and such a change also has implications for translation support.