Hi, After a bit of reading, it occurred to me that it was looking for variables related to Secure Boot (moksbstate), when I didn't have Secure Boot enabled, although I was booting in UEFI; I was previously running Mint 18.x, which refused to boot at all with the NVidia drivers if Secure Boot was enabled.
So, I've now enabled Secure Boot, set the MOK, rebooted a couple of times, & all is now well, the shim-signed package has sorted itself out. I don't know whether you feel this still merits attention as an edge case that could be handled a little more gracefully? but in this instance I'm now back in business & all is looking good. Hope this helps, Dave. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766729 Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1766729/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
