The output in your dpkg log shows:
Setting up shim-signed (1.34.9+13-0ubuntu2) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
Generating a new Secure Boot signing key:
Generating a 2048 bit RSA private key
.................................................+++
......................................................+++
writing new private key to '/var/lib/shim-signed/mok/MOK.priv'
-----
asdfas
dfasdf
sdfa
sdf
asdf
asdf
asdf
asdf
afsd
Terminated
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess was killed
by signal (Terminated)
This suggests that you were prompted via debconf to enter a password for use
with MokManager to configure a machine owner key in your UEFI firmware; but
instead of answering the password prompt, you tried to enter text at the
terminal.
I can see from the information attached to the bug that this is a Dell
system that shipped with Ubuntu preinstalled. What I can't see is how
you did this upgrade, or why you did not see the debconf prompt. Can
you provide more information about how you did this upgrade?
** 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/1770905
Title:
package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
installed shim-signed package post-installation script subprocess was
killed by signal (Terminated)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1770905/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
