(Ubuntu 16.04, non-UEFI) package shim-signed 1.19~16.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shim-signed (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
hi
i tried to download clam tk and the bug warning appeared
i hope that i have ticked the security button therefore correctly
with kind regards
a. kracht
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.19~16.
ProcVersionSign
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
BootEFIContents:
fw
fwupx64.efi
Date: Sun Jan 1 13:30:15 2017
DpkgHistoryLog:
Start-Date: 2017-01-01 13:30:08
Commandline: aptdaemon role='role-
Install: libjson-perl:amd64 (2.90-1, automatic), libtext-
DuplicateSignature:
package:
Setting up grub-efi-
grub-install: error: /usr/lib/
dpkg: error processing package grub-efi-
subprocess installed post-installation script returned error exit status 1
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.4ubuntu1.1
apt 1.2.15ubuntu0.2
SourcePackage: shim-signed
Title: package shim-signed 1.19~16.
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
summary: |
- package shim-signed 1.19~16.04.1+0.8-0ubuntu2 failed to install/upgrade: - subprocess installed post-installation script returned error exit status - 1 + (Ubuntu 16.04, non-UEFI) package shim-signed 1.19~16.04.1+0.8-0ubuntu2 + failed to install/upgrade: subprocess installed post-installation script + returned error exit status 1 |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.