package shim-signed 1.34.6+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 5

Bug #1766564 reported by shemgp
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Upgraded packages and this error showed up.
I had to reinstall dkms to make it work again.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.6+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-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-0ubuntu6
Architecture: amd64
Date: Tue Apr 24 19:02:19 2018
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 5
InstallationDate: Installed on 2015-09-28 (938 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
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.6+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 5
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
shemgp (shemgp) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Thanks for filing a bug and helping to make Ubuntu better!

I believe the bug you have filed should be resolved with the new version of shim-signed:

shim-signed (1.34.7) bionic; urgency=medium

  * debian/shim-signed.postinst: it's not guaranteed that all linux-image
    packages currently installed have dkms modules built for them.
    Gracefully handle any failures in the path for signing existing dkms
    modules on upgrade due to absent modules. LP: #1766391.
  * Add a dependency on sbsigntool for kmodsign, which we use directly.

With that being the case, could you confirm that when you upgrade to this package you are correctly prompted for a password to enroll a new MOK key?

Changed in shim-signed (Ubuntu):
status: New → Incomplete
tags: removed: need-duplicate-check
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.