[Bug 1766273] Re: package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Steve Langasek
steve.langasek at canonical.com
Mon Apr 23 16:41:01 UTC 2018
Thank you for reporting this issue. The error in your logs is:
DKMS: install completed.
Adding '/var/lib/shim-signed/mok/MOK.der' to shim:
mv: cannot stat '/var/lib/shim-signed/dkms-list.new': No such file or directory
dpkg: error processing package shim-signed (--configure):
installed shim-signed package post-installation script subprocess returned error exit status 1
This is the same bug as LP: #1765939, which we do not yet understand.
Is there something about your system that would explain why the /var/lib
/shim-signed/dkms-list.new file created at the beginning of this
command's run is missing by the end of the command's run?
Regarding the reboot experience: this error happened after the shim-
signed package has already written the required instructions into your
firmware's nvram, which means that on your next boot (not on shutdown)
you should have been prompted to confirm the configuration. If you were
not, that may point to a problem with your firmware being incompatible
with MokManager. Can you tell me if the file /sys/firmware/efi/efivars
/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23 exists on your
system?
** Changed in: shim-signed (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1766273
Title:
package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade:
installed shim-signed package post-installation script subprocess
returned error exit status 1
Status in shim-signed package in Ubuntu:
Incomplete
Bug description:
This occurred after I rebooted after an update on April 23 2018. After
the update, I was prompted to create a password for something
regarding UEFI secure booting, and the prompt said I would be asked
for this password when rebooting. When I rebooted, however, I was not
asked for the password, and had to force a shutdown. I booted normally
next time, except for receiving this error message. I don't know for
certain if these events are related.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.4+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: Mon Apr 23 08:50:45 2018
EFITables:
Apr 23 10:51:03 rob-Lenovo-Y50-70 kernel: efi: EFI v2.31 by INSYDE Corp.
Apr 23 10:51:03 rob-Lenovo-Y50-70 kernel: efi: ACPI=0x9cffe000 ACPI 2.0=0x9cffe014 SMBIOS=0x9cebef98
Apr 23 10:51:03 rob-Lenovo-Y50-70 kernel: secureboot: Secure boot enabled
Apr 23 10:52:25 rob-Lenovo-Y50-70 fwupd[1968]: disabling plugin because: failed to startup uefi: UEFI firmware updating not supported
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-01-06 (107 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.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.4+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-03-28 (26 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1766273/+subscriptions
More information about the foundations-bugs
mailing list