So the issue here appears to be that the new shim treats a failure to
write MokListRT to nvram as a fatal error, even when not booting in
SecureBoot mode, with the consequence that systems with no nvram space
available will fail to boot.
This will take time to resolve upstream due to the requirement to go
through a signing cycle with Microsoft for any new binaries. However,
it sounds like the bug is well-characterized and we should be able to
work with upstream for a proper fix.
** Changed in: shim (Ubuntu)
Status: Incomplete => Triaged
** Changed in: shim-signed (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid Parameter
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
