@Thorsten, Secure Boot enforcement being disabled is indeed one. Being in Setup Mode is another. Updates may have been missing on the system too (since things only happen provided that you have installed the relevant update that ships the change). Also, as per this bug, one could also be explicitly asking grub to load via linuxefi an unsigned kernel binary. The point is that until you are sure what this particular issue is, it is better to open a new bug. This is done to avoid muddying the waters with unrelated issues, and help us avoid "forgetting" to fix something because it was one slightly different issue on an unrelated bug.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401532 Title: GRUB's Secure Boot implementation loads unsigned kernel without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
