This problem still exists in my apt-get-upgrad'ed copy of yakkety and plagues me on my Lenovo E560 with up-to-date (from Lenovo's point of view) firmware.
Is there a step-by-step for the workaround (patching, building and replacing MokManager.efi's)? It seems to me that even when the fixed MokManager gets into the repos, people will still need to go back and update any UEFIs they've deployed, to be able to turn Secure Boot back on, right? Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600452 Title: "Failed to set variable: (2) Invalid Parameter" when enrolling MOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/1600452/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
