Ubuntu
shim-signed package

  1. Bug #1800274
  2. Comment #2

Comment 2 for bug 1800274

Revision history for this message
Steve Langasek (vorlon) wrote : Re: package shim-signed 1.37~18.04.2+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

The error in your log is:

Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ...
/etc/kernel/header_postinst.d/dkms:
debconf: unable to initialize frontend: Passthrough
debconf: (Cannot connect to /tmp/aptdaemon-0_mjm70h/debconf.socket: Connection refused at (eval 17) line 3.)
debconf: falling back to frontend: Noninteractive
debconf: unable to initialize frontend: Passthrough
debconf: (Cannot connect to /tmp/aptdaemon-0_mjm70h/debconf.socket: Connection refused at (eval 17) line 3.)
debconf: falling back to frontend: Noninteractive
Running in non-interactive mode, doing nothing.
--- /var/lib/shim-signed/dkms-list 2018-10-27 11:38:13.686363404 +0200
+++ /var/lib/shim-signed/dkms-list.new 2018-10-27 11:38:13.686363404 +0200
@@ -1,5 +1,2 @@
 /var/lib/dkms
-/var/lib/dkms/i915-4.8-4.4
-/var/lib/dkms/nvme-apst
-/var/lib/dkms/oem-wifi-qualcomm-ath10k-lp1734600-4.4
 /var/lib/dkms/virtualbox

It appears you have dkms modules installed and it was determined that you needed to be prompted to register a MOK in your firmware, but because the gnome session crashed, taking the upgrader frontend with it, you could not be prompted, leading to this error.

This does look like a bug in shim-signed, though. The intent of this code is that we should only error out if there are *added* dkms modules and we don't have a MOK. In this case, there are only *removed* modules. So it should not be considered an error, but the code doesn't actually distinguish between additions and removals.

To work around this failure, you should run 'sudo dpkg --configure -a' from a terminal to follow the prompts and fully enroll a MOK.