Ubuntu
grub2-signed package

package grub-efi-amd64-signed 1.110.2+2.02+dfsg1-5ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

Bug #1816249 reported by Kacper Kaczmarczyk on 2019-02-16

This bug report is a duplicate of: Bug #1805490: [master] Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required. / Could not delete variable: Invalid argument". Edit Remove

This bug affects 9 people

Affects		Status	Importance	Assigned to	Milestone
	grub2-signed (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

idk

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: grub-efi-amd64-signed 1.110.2+2.02+dfsg1-5ubuntu8.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Sat Feb 16 09:51:31 2019
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-02-07 (8 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu5
apt 1.7.2
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.110.2+2.02+dfsg1-5ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Kacper Kaczmarczyk (kofalinux) wrote on 2019-02-16:

AptOrdering.txt Edit (599 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Df.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (101.5 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (132.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (5.2 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (530 bytes, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2019-02-16

tags:

removed: need-duplicate-check

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-02-19:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2-signed (Ubuntu):
status:	New → Confirmed

Revision history for this message

Justin Philpott (azurejp) wrote on 2019-02-21:

For me I can give some context:
- DELL XPS 9370
- Installed 18.04, dual boot, part of which I think meant that I needed secure boot (may be wrong)
- Attempted to upgrade Kernel to fix some bluetooth issues (known bugs) using UKUU
- Kernel install went OK, grub updated, but then on reboot the system complains that the kernel is not signed
- Attempted upgrade to 18.10, failed on same issue to new kernel not being signed
- But rebooted and checked kernel and it had updated OK to 4.18...
Thanks all I know... hope it helps.

Revision history for this message

Steve Langasek (vorlon) wrote on 2021-07-21:

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 1805490, 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.