FYI, the contents of the SecureBoot efi variables show that SecureBoot is not enabled on this system at the time this was run. And the efibootmgr output shows that grub is being booted directly, not going through shim-signed, which would not be valid if SecureBoot is enabled. So it looks like this is a problem with shim+grub not being configured correctly on installation.
** Package changed: shim (Ubuntu) => grub-installer (Ubuntu) ** Changed in: grub-installer (Ubuntu) Importance: Undecided => High ** Changed in: grub-installer (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184297 Title: Secure boot failed, claiming boot is against security policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1184297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs