package shim-signed 1.34.9+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
Error installing package after 18.04 upgrade
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.9+13-0ubuntu2
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
.proc.sys.
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat May 5 11:21:25 2018
EFITables:
may 06 08:45:49 joze-Lenovo-B50-80 kernel: efi: EFI v2.40 by INSYDE Corp.
may 06 08:45:49 joze-Lenovo-B50-80 kernel: efi: SMBIOS=0x9c5ca000 ESRT=0x9c5c8e18 ACPI 2.0=0x9cffe014
may 06 08:45:49 joze-Lenovo-B50-80 kernel: secureboot: Secure boot could not be determined (mode 0)
may 06 08:45:49 joze-Lenovo-B50-80 kernel: esrt: Reserving ESRT space from 0x000000009c5c8e18 to 0x000000009c5c8e50.
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2016-08-14 (629 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
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: 6 0 0 0 0
SourcePackage: shim-signed
Title: package shim-signed 1.34.9+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-05-05 (0 days ago)
| Jose (jose-morell) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
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 #1767276, 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.