(Ubuntu 16.10, non-UEFI) package shim-signed 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| shim-signed (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I've done nothing, just updated from 16.04 32 to 16.10 64.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: shim-signed 1.21.3+
ProcVersionSign
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
shim:amd64: Install
shim-signed:amd64: Install
NULL: ConfigurePending
Architecture: amd64
BootEFIContents:
fw
fwupx64.efi
Date: Sat Nov 5 16:51:58 2016
Df:
Файл.система 1K-блоков Использовано Доступно Использовано% Cмонтировано в
/dev/sda1 957260436 7760048 900851328 1% /
/dev/sdb 1556480 1556480 0 100% /cdrom
udev 1961244 0 1961244 0% /dev
tmpfs 395452 21588 373864 6% /run
EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system.
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageV
dpkg 1.18.10ubuntu1
apt 1.3.1
SourcePackage: shim-signed
Title: package shim-signed 1.21.3+
UpgradeStatus: No upgrade log present (probably fresh install)
| ЯR (yar-webdev) wrote | #1 |
| Steve Langasek (vorlon) wrote | #2 |
| ЯR (yar-webdev) wrote | #3 |
| summary: |
- package shim-signed 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3 failed - to install/upgrade: subprocess installed post-installation script - returned error exit status 1 + (Ubuntu 16.10, non-UEFI) package shim-signed + 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3 failed to install/upgrade: + subprocess installed post-installation script returned error exit status + 1 |
Something has caused the shim-signed package to be installed on your system, despite your system not being detected as an EFI system. We have seen reports of this, but have yet to identify the source of the problem. Could you attach the output of 'sudo dmidecode' from your system? That might help.