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

Bug #1680283 reported by Marji Cermak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm running Ubuntu Gnome 17.04 (installed from beta 2 ISO) on Dell XPS 13 9360 (early 2017, bought in Australia).

I suspect this bug happened just during apt automatic upgrade after my computer booted.

$ lsb_release -rd
Description: Ubuntu Zesty Zapus (development branch)
Release: 17.04

$ apt-cache policy shim-signed
shim-signed:
  Installed: 1.27+0.9+1474479173.6c180c6-1ubuntu1
  Candidate: 1.27+0.9+1474479173.6c180c6-1ubuntu1
  Version table:
 *** 1.27+0.9+1474479173.6c180c6-1ubuntu1 500
        500 http://au.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: shim-signed 1.27+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
Date: Thu Apr 6 10:32:43 2017
DuplicateSignature:
 package:shim-signed:1.27+0.9+1474479173.6c180c6-1ubuntu1
 Processing triggers for shim-signed (1.27+0.9+1474479173.6c180c6-1ubuntu1) ...
 Running in non-interactive mode, doing nothing.
 dpkg: error processing package shim-signed (--configure):
  subprocess installed post-installation script returned error exit status 1
EFIBootMgr:
 BootCurrent: 0001
 Timeout: 0 seconds
 BootOrder: 0001
 Boot0000* Windows Boot Manager HD(1,GPT,155f043f-8730-4e5b-9e9c-755dcc61d4ab,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...K................
 Boot0001* ubuntu HD(1,GPT,cc91ec4b-3224-4151-9e2a-1f2345c5f2ab,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-03-31 (5 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.4
SourcePackage: shim-signed
Title: package shim-signed 1.27+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
Marji Cermak (cermakm) 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 #1675870, 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
Steve Langasek (vorlon)
summary: - package shim-signed 1.27+0.9+1474479173.6c180c6-1ubuntu1 failed to
- install/upgrade: subprocess installed post-installation script returned
- error exit status 1
+ (unattended-upgrades) package shim-signed
+ 1.27+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade:
+ subprocess installed post-installation script returned error exit status
+ 1
Revision history for this message
Steve Langasek (vorlon) wrote :

You should be able to resolve this issue by running 'sudo apt -f install' from a terminal and following the prompts.

I notice that it appears you installed the virtualbox package from the commandline on 1 Apr; you should have already been prompted at that time to disable secureboot. Did you see the messages at that time? Did you deliberately choose not to disable secureboot? That leaves your system in an inconsistent state, where you have dkms module packages installed which cannot be used on a secureboot-enabled system, but you have not chosen to disable secureboot.

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.