Bug ID 1189841
Summary Secure Boot certificate no longer queued for import into MOK
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee msuchanek@suse.com
Reporter jeffm@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Since kernel-source commit 18f65dfce6af8bef50878fb80ba29f6d8626a918,
automatically queuing the secure boot certificate isn't happening.

This is because the post.sh changes cause the scriptlet to exit unconditionally
but the secure boot handling adds to the end of the script after the exit:

[...]

# check if something failed
[ $wm2_rc != 0 ] && exit $wm2_rc
exit $rc

# vim: set sts=4 sw=4 ts=8 noet:
if ! command -v mokutil >/dev/null; then
        exit 0
fi

[...]

This change has also been adopted in SLE.


You are receiving this mail because: