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

Bug #1698904 reported by Shelley Dewar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

shows only on startup

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
.sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: 

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

When you last applied the upgrades to your system, how were these done? The only logs present show an apt-get upgrade, which should have interactively prompted you about the combination of dkms and secureboot. But this failure shows that shim-signed could not prompt you due to a lack of debconf frontend. This usually happens only when using graphical package managers, not when using apt-get upgrade directly.

Changed in shim-signed (Ubuntu):
status: New → Incomplete
Revision history for this message
Shelley Dewar (shelmarae) wrote : Re: [Bug 1698904] Re: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

These updates were part of the automatic downloading and updating. Was probably just an error. If it seems serious, let me know

----- Original Message -----

From: "Steve Langasek" <email address hidden>
To: <email address hidden>
Sent: Monday, June 19, 2017 2:22:02 PM
Subject: [Bug 1698904] Re: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

When you last applied the upgrades to your system, how were these done?
The only logs present show an apt-get upgrade, which should have
interactively prompted you about the combination of dkms and secureboot.
But this failure shows that shim-signed could not prompt you due to a
lack of debconf frontend. This usually happens only when using
graphical package managers, not when using apt-get upgrade directly.

** Changed in: shim-signed (Ubuntu)
Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1698904

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

Status in shim-signed package in Ubuntu:
Incomplete

Bug description:
shows only on startup

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
.sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1698904/+subscriptions

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

Ok, the logs attached to your bug report suggest this was not entirely automatic; the completely automated process would show up as 'unattended-upgrades', but that doesn't show in your log. Was there no GUI presented to you when this update was happening?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]

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