This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.10
---------------
dkms (2.2.0.3-1.1ubuntu5.14.04.10) trusty; urgency=medium
* debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
at kernel update times. (LP: #1772950)
- Generate a new MOK if there isn't one yet, and use that so sign
newly-built kernel modules. (LP: #1748983)
* debian/control: Breaks: shim-signed (<< 1.33.1~14.04.4) to ensure both
are updated in lock-step since the changes above require a new version of
update-secureboot-policy to correctly generate the new MOK and enroll it
in firmware.
-- Mathieu Trudel-Lapierre <cypher...@ubuntu.com> Mon, 28 Jan 2019
11:05:49 -0500
** Changed in: dkms (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772950
Title:
dkms key enrolled in mok, but dkms module fails to load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1772950/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
