package grub-efi-amd64-signed 1.187.3~22.04.1+2.06-2ubuntu14.1 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32

Bug #2019950 reported by Edwin Harris
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have recently rearranged my hard drives, adding an nvme drive as my master boot and removing two sata HDDs. The old master boot SSD is now a backup drive but still contains a bootable partition.

After an absence of 4 weeks where the system was running I logged in to find software updater listing outstanding updates and a message saying that "Snap"snap-store" is refreshing now!". I clicked update now, which it did and then presented another list of software to update.

During this second software update the system was configuring grub-efi-amd64-signed, a window opened listing my two remaining drives asking me to tick "GRUB install devices". I twice ticked the nvme drive and then next and it asked whether I wanted to "continue without installing GRUB?" I left this unticked then next and it took me back to the first screen. The third time I ticked both drives then next and it initiated this crash report. I do not know what the error exit status was as it was not displayed.

On a second, identical, system same scenario but this time the grub update was part of the first software update and again I ticked only the nvme drive but then ticked continue without installing GRUB and it went through to completion, again bringing up a second list of software to update.

One difference between the two systems - the Snap store message on the system that failed had an icon to the left showing a no-entry sign whereas the second system this icon showed an origami bird.

After the second update the second system requested a reboot which I did and it completed successfully.

Both systems as Ryzen 9 3900 running Ubuntu 22.04.2 LTS, the first system having 64GB ram and the second system having 16GB ram.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: grub-efi-amd64-signed 1.187.3~22.04.1+2.06-2ubuntu14.1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed May 17 10:38:51 2023
DuplicateSignature:
 package:grub-efi-amd64-signed:1.187.3~22.04.1+2.06-2ubuntu14.1
 Setting up grub-efi-amd64-signed (1.187.3~22.04.1+2.06-2ubuntu14.1) ...
 mount: /var/lib/grub/esp: special device /, does not exist.
 dpkg: error processing package grub-efi-amd64-signed (--configure):
  installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
InstallationDate: Installed on 2022-12-21 (146 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt 2.4.9
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.187.3~22.04.1+2.06-2ubuntu14.1 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
UpgradeStatus: Upgraded to jammy on 2022-12-21 (146 days ago)

Revision history for this message
Edwin Harris (tedh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2015401, so 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.

tags: removed: need-duplicate-check
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.