Comment 8 for bug 1600452

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,