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)

[Dan Egnor]

Got an error notification after software-updater ran

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.9+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat May 5 17:46:10 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
EFITables:
 May 12 17:36:31 egnor-xps kernel: efi: EFI v2.40 by American Megatrends
 May 12 17:36:31 egnor-xps kernel: efi: ACPI=0x3f0c3000 ACPI 2.0=0x3f0c3000 SMBIOS=0xf0000 SMBIOS 3.0=0xf0020 ESRT=0x3fdd9018 MEMATTR=0x3c2bb018
 May 12 17:36:31 egnor-xps kernel: secureboot: Secure boot disabled
 May 12 17:36:31 egnor-xps kernel: esrt: Reserving ESRT space from 0x000000003fdd9018 to 0x000000003fdd9050.
ErrorMessage: installed shim-signed package post-installation script subprocess was killed by signal (Terminated)
InstallationDate: Installed on 2018-04-22 (20 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
MokSBStateRT: 6 0 0 0 1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.1
SecureBoot: 6 0 0 0 1
SourcePackage: shim-signed
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)
UpgradeStatus: Upgraded to bionic on 2018-05-06 (6 days ago)

[Steve Langasek (vorlon)]

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?

[Dan Egnor (egnor)]

Oh my that's a little crazy.

Yes, this is a Dell XPS 13 laptop.

I was upgrading from Ubuntu 16.04 (which the laptop came from Dell with) to 18.04, using the normal update process with X running. During the upgrade process, it seemingly hung at the shim-signed point. There was no visible password prompt anywhere. I remember trying to type various things at the console to no avail. Eventually I killed the upgrade, which left things in a little bit of a sad state, and I finished the upgrade from the console, which worked.

After fixing everything up with the newly upgraded OS, some time later, I got a prompt to report a system problem. I clicked the button to go ahead and report it, because that seemed like the helpful thing to do. I had no idea it was reporting the problem that happened way back during the original upgrade process.

It *was* a real problem, but feel free to discard this bug if there isn't enough data to be useful!

[Steve Langasek (vorlon)]

What do you consider the "normal" update process? Did you run update-manager -d? do-release-upgrade -d? apt dist-upgrade?

[Dan Egnor (egnor)]

Sorry, I'm fairly certain it was "do-release-upgrade -d".

[Steve Langasek (vorlon)]

Thanks. What is the output of 'debconf-show debconf'?

[Dan Egnor (egnor)]

% sudo debconf-show debconf
  debconf/frontend: Dialog
  debconf-apt-progress/media-change:
  debconf-apt-progress/info:
  debconf-apt-progress/preparing:
  debconf/priority: high
  debconf-apt-progress/title:

[Steve Langasek (vorlon)]

> debconf/frontend: Dialog

Ok that looks completely as expected. So unfortunately I don't know what has happened here and why the debconf prompts were shown to you.

[Launchpad Janitor (janitor)]

[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]