That's not the sort of config we usually turn on, as it's more of a developer feature than something end users are interested in. So I don't see any need to turn the option back on. We can go ahead and grab the patch though.
In any case I'd like to get some secure boot testing with the current build, as we'd like to try and get a 5.10 build into hirsute-proposed next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
