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

Bug #1679366 reported by Jaime Cruz
380
This bug affects 83 people
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
High
Mathieu Trudel-Lapierre
update-manager (Ubuntu)
High
Mathieu Trudel-Lapierre

Bug Description

Crash while updating.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Apr 3 18:17:35 2017
DpkgHistoryLog:
 Start-Date: 2017-04-03 18:16:50
 Commandline: aptdaemon role='role-upgrade-system' sender=':1.83'
 Upgrade: grub-common:amd64 (2.02~beta2-36ubuntu3.8, 2.02~beta2-36ubuntu3.9), grub2-common:amd64 (2.02~beta2-36ubuntu3.8, 2.02~beta2-36ubuntu3.9), grub-efi-amd64-bin:amd64 (2.02~beta2-36ubuntu3.8, 2.02~beta2-36ubuntu3.9), grub-efi-amd64:amd64 (2.02~beta2-36ubuntu3.8, 2.02~beta2-36ubuntu3.9), shim-signed:amd64 (1.19~16.04.1+0.8-0ubuntu2, 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1), grub-efi-amd64-signed:amd64 (1.66.8+2.02~beta2-36ubuntu3.8, 1.66.9+2.02~beta2-36ubuntu3.9), shim:amd64 (0.8-0ubuntu2, 0.9+1474479173.6c180c6-1ubuntu1)
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-09-06 (940 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
SourcePackage: shim-signed
Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-03-05 (29 days ago)

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

The error in the logs is:

> 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 appears to indicate that your system has dkms modules installed, and therefore must have secureboot administratively disabled in order to ensure your system remains bootable, but because this was a non-interactive upgrade, shim-signed was unable to prompt you about this.

It also appears that the signed kernel package is missing from your system, which would also prevent secureboot from working.

I recommend that you install the linux-signed-image-generic package on your system.

Do you know if you have dkms modules installed on your system? (/var/lib/dkms)

Changed in shim-signed (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shim-signed (Ubuntu):
status: New → Confirmed
Revision history for this message
Jaime Cruz (jaime-cruz) wrote :

Yes, I have VirtualBox installed on this system which has DKMS modules installed.

Changed in shim-signed (Ubuntu):
importance: Undecided → High
Revision history for this message
Steve Langasek (vorlon) wrote :

Thanks, Jaime. Can you also tell us how you did this upgrade? Was it an automatic, unattended upgrade, or did you use a graphical frontend - and if so, which one?

Revision history for this message
Jaime Cruz (jaime-cruz) wrote :

I ran the default Ubuntu Software Updater and selected the choice to upgrade my system. It wasn't unattended as it did pause at several points to ask questions before proceeding.

Revision history for this message
Steve Langasek (vorlon) wrote :

should be fixable by update-manager pulling in libgtk2-perl for the debconf frontend.

summary: - package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed
- to install/upgrade: subprocess installed post-installation script
- returned error exit status 1
+ (update-manager) package shim-signed
+ 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade:
+ subprocess installed post-installation script returned error exit status
+ 1
Changed in update-manager (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in shim-signed (Ubuntu):
status: Confirmed → Invalid
Changed in update-manager (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
Jaime Cruz (jaime-cruz) wrote :

I don't know when it was installed, but I apparently already have libgtk2-perl Version 2:1.2498-1 on my system.

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1679366] Re: (update-manager) package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

On Tue, Apr 11, 2017 at 11:42:18AM -0000, Jaime Cruz wrote:
> I don't know when it was installed, but I apparently already have
> libgtk2-perl Version 2:1.2498-1 on my system.

Interesting, possibly because this system was originally installed with
14.04. This does mean changing update-manager, while correct, is unlikely
to solve your reported problem. It also means I don't know how to solve
your particular problem, since update-manager with libgtk2-perl installed
works here for me.

Revision history for this message
Austin Dempewolff (adempewolff) wrote :

I had the same crash while using the additional drivers GUI to switch the the proprietary nvidia drivers.

Revision history for this message
Steve Langasek (vorlon) wrote :

On Tue, Apr 18, 2017 at 01:44:03AM -0000, Austin Dempewolff wrote:
> I had the same crash while using the additional drivers GUI to switch
> the the proprietary nvidia drivers.

That is bug #1679784.

Revision history for this message
firat (e73kiel) wrote :

Had the crash on first update. Before that default installed nouveau driver is changed with nvidia-driver.

Revision history for this message
emailtheds (emailtheds) wrote :

This issue sounds similar to bug 1679784.

Using "Software & Updates" to switch between Nouveau and Nvidia 375.39 video drivers. Secure boot is enabled on this computer, but received no prompt to disable it.

(Note: It looks like a fix is in progress for Yakkety, but not yet applied to Xenial.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers