package shim-signed 1.40.4+15+1552672080.a4a1fbe-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) |
Expired
|
Undecided
|
Unassigned |
Bug Description
unexpected crash app
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: shim-signed 1.40.4+
ProcVersionSign
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckR
Date: Thu Sep 17 17:15:43 2020
DuplicateSignature:
package:
Setting up shim-signed (1.40.4+
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess returned error exit status 1
EFIBootMgr:
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0003
Boot0002* ubuntu HD(1,GPT,
Boot0003* Windows Boot Manager HD(1,GPT,
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-09-12 (5 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Missing: /boot/efi/
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.3
SourcePackage: shim-signed
Title: package shim-signed 1.40.4+
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
The error in your log is:
Setting up grub-efi- amd64-signed (1.142. 6+2.04- 1ubuntu26. 4) ... 15+1552672080. a4a1fbe- 0ubuntu2) ...
Trying to migrate /boot/efi into esp config
Setting up shim-signed (1.40.4+
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess returned error exit status 1
It appears the 1.40.3 version of shim-signed had successfully been configured before this, and there are no packaging changes between 1.40.3 and 1.40.4. And there is no output to explain what has failed. Is this problem reproducible if you run 'sudo dpkg --configure -a'?