Thank you for reporting this issue. The error in your logs is:
DKMS: install completed.
Adding '/var/lib/shim-signed/mok/MOK.der' to shim:
mv: cannot stat '/var/lib/shim-signed/dkms-list.new': No such file or directory
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess returned
error exit status 1
This is the same bug as LP: #1765939, which we do not yet understand.
Is there something about your system that would explain why the /var/lib
/shim-signed/dkms-list.new file created at the beginning of this
command's run is missing by the end of the command's run?
Regarding the reboot experience: this error happened after the shim-
signed package has already written the required instructions into your
firmware's nvram, which means that on your next boot (not on shutdown)
you should have been prompted to confirm the configuration. If you were
not, that may point to a problem with your firmware being incompatible
with MokManager. Can you tell me if the file /sys/firmware/efi/efivars
/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23 exists on your
system?
** Changed in: shim-signed (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766273
Title:
package shim-signed 1.34.4+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/shim-signed/+bug/1766273/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
