This bug hit me today (Debian Buster) and I have to say it's pretty egregious. I don't buy the pandemic certificate excuse as Debian development has always been decentralized. If Microsoft or Apple had done this the headlines would be about them bricking PCs or Macs.
This morning I rebooted my Dell server to apply a kernel security patch only for it to display the
Could not create MokListXRT: Out of Resources
Something has gone seriously wrong: import_mok_state() failed: Out of Resources
error message. Except, in my case, the machine simply powered off after the error. Fortunately Dell's BIOSes are pretty robust and I was able to boot in legacy mode and then apply the EFI path fix from https://askubuntu.com/a/1333772/932418. Purely from observation of this and the AskUbuntu thread it seems ThinkPad users are not that lucky.
What steps can be taken to ensure this doesn't happen again?
This bug hit me today (Debian Buster) and I have to say it's pretty egregious. I don't buy the pandemic certificate excuse as Debian development has always been decentralized. If Microsoft or Apple had done this the headlines would be about them bricking PCs or Macs.
This morning I rebooted my Dell server to apply a kernel security patch only for it to display the
Could not create MokListXRT: Out of Resources
Something has gone seriously wrong: import_mok_state() failed: Out of Resources
error message. Except, in my case, the machine simply powered off after the error. Fortunately Dell's BIOSes are pretty robust and I was able to boot in legacy mode and then apply the EFI path fix from https:/ /askubuntu. com/a/1333772/ 932418. Purely from observation of this and the AskUbuntu thread it seems ThinkPad users are not that lucky.
What steps can be taken to ensure this doesn't happen again?