Ubuntu
shim-signed package

  1. Bug #1936759
  2. Comment #10

Comment 10 for bug 1936759

Revision history for this message
Jacques Williamson (jckbuntu) wrote :

With shim-signed 1.48+15.4-0ubuntu5 installed and secure boot enabled, I also ran:
$ sudo mokutil --set-verbosity true
... rebooted, and captured output in a video as requested. See here (attaching to this ticket failed):
https://drive.google.com/file/d/1TBqolT2q552pK8RnDnMI7n7nIo0q8c9K/view?usp=sharing

I notice in the output there are references to "VMware", possibly relevant, I did follow steps very similar to this post (importing a self signed cert with mokutil) a while ago in order to get VMware to work:
https://communities.vmware.com/t5/VMware-Workstation-Player/VMMON-and-VMNET-Unable-to-install-modules-after-VMware-16-1-0/m-p/2836493/highlight/true#M36511

However, no previous signed shim version had any issues with this. Did Microsoft start signing shim's with new PKI data recently that my Dell UEFI firmware doesn't know about yet? (new secure boot keys?)

Thanks for your help in looking through my report.