This bug was fixed in the package shim-signed - 1.37~18.04.6
---------------
shim-signed (1.37~18.04.6) bionic; urgency=medium
* Pass --timeout -1 to mokutil in a separate mokutil run (LP: #1869187)
thanks to Aleksander Miera for the patch.
shim-signed (1.37~18.04.5) bionic; urgency=medium
* Fix versioned dependency on mokutil so that it matches the version in
bionic-updates. LP: #1862632.
shim-signed (1.37~18.04.4) bionic; urgency=medium
* Pass --timeout -1 to mokutil so that users don't end up with broken
systems by missing MokManager on reboot after install. LP: #1856422.
* Add a versioned dependency on the mokutil that introduces --timeout.
-- Matthieu Clemenceau <matthieu.clemenc...@canonical.com> Fri, 10 Jul
2020 14:27:41 -0500
** Changed in: shim-signed (Ubuntu Bionic)
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/1856422
Title:
always call mokutil with --timeout -1 when enrolling dkms keys
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1856422/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
