[Bug 2061837] Re: MOK enrollment is not adequately explained
Launchpad Bug Tracker
2061837 at bugs.launchpad.net
Thu Aug 15 15:21:59 UTC 2024
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
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/2061837
Title:
MOK enrollment is not adequately explained
Status in subiquity:
New
Status in ubiquity package in Ubuntu:
Confirmed
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)
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 09:19:07 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2024-04-16 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2061837/+subscriptions
More information about the foundations-bugs
mailing list