package shim-signed 1.42+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shim-signed (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
dont found the archive
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: shim-signed 1.42+15+
ProcVersionSign
Uname: Linux 5.4.0-42-generic x86_64
.proc.sys.
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootEFIContents:
BOOTX64.CSV
grub.cfg
grubx64.efi
mmx64.efi
shimx64.efi
CasperMD5CheckR
Date: Tue Aug 11 07:28:52 2020
Df:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda4 228673932 8060836 208927416 4% /
udev 6032716 0 6032716 0% /dev
tmpfs 1214084 1316 1212768 1% /run
/dev/sda1 523248 7984 515264 2% /boot/efi
EFITables:
ago 11 07:32:30 soporte kernel: efi: EFI v2.31 by American Megatrends
ago 11 07:32:30 soporte kernel: efi: ACPI=0xd9d36000 ACPI 2.0=0xd9d36000 SMBIOS=0xf04c0 MPS=0xfd420
ago 11 07:32:30 soporte kernel: secureboot: Secure boot disabled
ago 11 07:32:30 soporte kernel: secureboot: Secure boot disabled
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-08-07 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SecureBoot: 22 0 0 0 0
SourcePackage: shim-signed
Title: package shim-signed 1.42+15+
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1928352, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.