package shim-signed 1.34.7+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shim-signed (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
During update to Ubuntu 18.04
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.7+13-0ubuntu2
ProcVersionSign
Uname: Linux 4.15.0-19-generic x86_64
.proc.sys.
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Tue Apr 24 20:14:35 2018
DuplicateSignature:
package:
Processing triggers for shim-signed (1.34.7+
No MOK found.
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess returned error exit status 1
EFITables:
Apr 24 20:18:58 begesein-
Apr 24 20:18:58 begesein-
Apr 24 20:18:58 begesein-
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2017-11-30 (145 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.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
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.1
SecureBoot: 22 0 0 0 0
SourcePackage: shim-signed
Title: package shim-signed 1.34.7+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1766627, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.