This is definitively not a bug in the Ubuntu grub2 package. You have
installed a third-party tool, on which the Ubuntu developers have never
been consulted, that redirects the grub installation and claims to be
more secure, but has not tracked the evolution of SecureBoot support in
Ubuntu over the past 5 years.
Use of custom SecureBoot key databases and self-signed binaries is fine,
but where this is incompatible with the Ubuntu grub2 package, this is
not supported.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890672
Title:
secure boot fails after upgrade to grub2-common 2.04-1ubuntu26.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1890672/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
