package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10

[Philipp Flüs]

?

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-efi-amd64-signed 1.142+2.04-1ubuntu26
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Apr 22 17:09:37 2020
DuplicateSignature:
 package:grub-efi-amd64-signed:1.142+2.04-1ubuntu26
 Setting up grub-efi-amd64-signed (1.142+2.04-1ubuntu26) ...
 dpkg: error processing package grub-efi-amd64-signed (--configure):
  installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10
InstallationDate: Installed on 2015-07-26 (1732 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 10
UpgradeStatus: Upgraded to focal on 2020-04-22 (0 days ago)

[Launchpad Janitor (janitor)]

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

[Justin Iozzo (jriozzo)]

I had the same problem. This was fixed for me by installing grub-efi-amd64

[Víctor Gonzalo (vic.thor)]

I've tracked the error down to:
/usr/lib/grub/grub-multi-install:243
  db_fget grub-efi/install_devices seen

Which "rets": "10 grub-efi/install_devices doesn'\''t exist"
So it returns 10 and the whole thing collapses from there.

[James Dingwall (a-james-launchpad)]

On a problematic system this returns no values:

# debconf-get-selections | grep grub-efi

On another focal system the output is:

grub-efi-amd64 grub2/kfreebsd_cmdline_default string quiet splash
grub-efi-amd64 grub2/update_nvram boolean true
grub-efi-amd64 grub2/kfreebsd_cmdline string
grub-efi-amd64 grub2/device_map_regenerated note
grub-efi-amd64 grub-efi/install_devices multiselect /dev/disk/by-id/a-block-device
grub-efi-amd64 grub-efi/install_devices_disks_changed multiselect
grub-efi-amd64 grub-efi/install_devices_empty boolean false
grub-efi-amd64 grub2/no_efi_extra_removable boolean false
grub-efi-amd64 grub2/linux_cmdline_default string
grub-efi-amd64 grub-efi/install_devices_failed boolean false
grub-efi-amd64 grub2/unsigned_kernels note
grub-efi-amd64 grub2/linux_cmdline string

My problematic system was installed via debootstrap, the one that is ok by release-upgrade from bionic.

[James Dingwall (a-james-launchpad)]

I manually set the grub-efi/install_devices with the following command where G1 and G2 were set to my two ESP devices.

echo grub-efi-amd64 grub-efi/install_devices multiselect $G1 $G2 | debconf-set-selections

With a `set -x` added in /usr/lib/grub/grub-multi-install it now complains about another unset value:

+ RET='10 grub-efi/partition_description doesn'\''t exist'
+ case ${_db_internal_line%%[ ]*} in
+ return 10

I guess either these variables have been wiped or were never set. Based on #3 I did this which resulted in a log of new debconf variables being set:

grub-efi-amd64 grub-efi/install_devices multiselect

Afterwards `apt-get -f install` completed the setup of grub-efi-amd64-signed

[James Dingwall (a-james-launchpad)]

#6 got a paste error, it should have been `dpkg-reconfigure grub-efi-amd64` to (re)populate the missing debconf configuration.