package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1680052 reported by Louis Romero
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

No idea. This popped up upon boot up and log in

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Tue Apr 4 14:50:56 2017
DpkgHistoryLog:
 Start-Date: 2017-04-04 14:50:04
 Commandline: aptdaemon role='role-upgrade-system' sender=':1.358'
 Upgrade: grub-common:amd64 (2.02~beta2-36ubuntu11, 2.02~beta2-36ubuntu11.2), grub2-common:amd64 (2.02~beta2-36ubuntu11, 2.02~beta2-36ubuntu11.2), grub-efi-amd64-bin:amd64 (2.02~beta2-36ubuntu11, 2.02~beta2-36ubuntu11.2), grub-efi-amd64:amd64 (2.02~beta2-36ubuntu11, 2.02~beta2-36ubuntu11.2), shim-signed:amd64 (1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3, 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1), grub-efi-amd64-signed:amd64 (1.74+2.02~beta2-36ubuntu11, 1.74.2+2.02~beta2-36ubuntu11.2), shim:amd64 (0.9+1465500757.14a5905.is.0.8-0ubuntu3, 0.9+1474479173.6c180c6-1ubuntu1)
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-02-22 (41 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.4
SourcePackage: shim-signed
Title: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Louis Romero (louis-romero) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1679617, 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.

tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

Thanks for reporting this issue.

The error in your logs is:

> Setting up shim-signed (1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1) ...
> Installing for x86_64-efi platform.
> Installation finished. No error reported.
> Running in non-interactive mode, doing nothing.
> dpkg: error processing package shim-signed (--configure):
> subprocess installed post-installation script returned error exit status 1

This indicates that the shim package detected dkms modules present on your system, and that you have SecureBoot enabled, and therefore SecureBoot must be administratively disabled in order for you to continue booting.

And the prompt failed to be displayed, so it was impossible to prompt you for this.

However, this should already have been the policy in place prior to your upgrade, so I'm not sure why you were prompted again. Could you please send the output of the following commands:
$ cat /proc/sys/kernel/moksbstate_disabled
$ od -tx1 /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
$ od -tx1 /sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23

Changed in shim-signed (Ubuntu):
status: New → Incomplete
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.