Ubuntu
grub2-signed package

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

Bug #1781367 reported by Alessandro Mambelli on 2018-07-12

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 1 person

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

Bug Description

Setting up grub-efi-amd64-signed (1.93.2+2.02-2ubuntu8.1) ...
Installing for x86_64-efi platform.
Could not delete variable: Invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Setting up cups-bsd (2.2.7-1ubuntu2.1) ...
Setting up libmagick++-6.q16-7:amd64 (8:6.9.7.4+dfsg-16ubuntu6.3) ...
Setting up libmagickcore-6.q16-3-extra:amd64 (8:6.9.7.4+dfsg-16ubuntu6.3) ...
Setting up imagemagick (8:6.9.7.4+dfsg-16ubuntu6.3) ...
Setting up libglx0:amd64 (1.0.0-2ubuntu2.1) ...
Setting up libimage-magick-perl (8:6.9.7.4+dfsg-16ubuntu6.3) ...
dpkg: dependency problems prevent configuration of shim-signed:
shim-signed depends on grub-efi-amd64-signed; however:
Package grub-efi-amd64-signed is not configured yet.

dpkg: error processing package shim-signed (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Setting up libgl1:amd64 (1.0.0-2ubuntu2.1) ...
Setting up libmutter-2-0:amd64 (3.28.2-2~ubuntu18.04.1) ...
Setting up libgl1-mesa-glx:amd64 (18.0.5-0ubuntu0~18.04.1) ...
Setting up gir1.2-mutter-2:amd64 (3.28.2-2~ubuntu18.04.1) ...
Setting up mutter (3.28.2-2~ubuntu18.04.1) ...
Setting up gnome-shell (3.28.2-0ubuntu0.18.04.1) ...
Setting up gdm3 (3.28.2-0ubuntu1.3) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64-signed 1.93.2+2.02-2ubuntu8.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jul 12 12:11:41 2018
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-05-08 (65 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu2
apt 1.6.2
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.93.2+2.02-2ubuntu8.1 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

Alessandro Mambelli (alessandro-mambelli) wrote on 2018-07-12:

AptOrdering.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Df.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (90.7 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (20.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (20.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")

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.