Ubuntu
shim-signed package

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

Bug #1690667 reported by pavly remon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
Incomplete
High
Unassigned

Bug Description

i have no information

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
.sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
.sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: 

Revision history for this message
pavly remon (pavlyremon) wrote :
Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

The error in your log is:

Processing triggers for shim-signed (1.28+0.9+1474479173.6c180c6-1ubuntu1) ...
debconf: unable to initialize frontend: Passthrough
debconf: (Cannot connect to /tmp/aptdaemon-b22qmfzw/debconf.socket: Connection refused at (eval 17) line 3.)
debconf: falling back to frontend: Noninteractive
Running in non-interactive mode, doing nothing.
dpkg: error processing package shim-signed (--configure):

Looks like something went wrong with aptdaemon's connection to the frontend.

How did you select the nvidia drivers for installation?

Changed in shim-signed (Ubuntu):
status: New → Incomplete
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.