[Bug 1931518] [NEW] grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI install
Ian Wienand
1931518 at bugs.launchpad.net
Thu Jun 10 03:59:06 UTC 2021
Public bug reported:
On our hosts we are seeing
---
$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up grub-efi-amd64-signed (1.167~18.04.1+2.04-1ubuntu44) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
Package grub-efi-arm64-signed is not installed.
dpkg: error processing package shim-signed (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
---
Indeed grub-install as called is failing
---
$ sudo grub-install --target=x86_64-efi --auto-nvram
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
---
This is a VM that is not booting via EFI
I feel pretty sure this has come in via
http://launchpadlibrarian.net/541948832/grub2-signed_1.167~18.04.1_1.167~18.04.3.diff.gz
* key on grub-efi-$(DEB_HOST_ARCH) as the binary package for
download-signed since grub-efi-* and grub2-common are now built from
separate sources.
This seemed to come in via our unatteneded upgrades @
---
Log started: 2021-06-02 06:52:59
files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.9-0ubuntu7.24_all.deb ...
Unpacking python3-apport (2.20.9-0ubuntu7.24) over (2.20.9-0ubuntu7.23) ...
Setting up python3-apport (2.20.9-0ubuntu7.24) ...
Setting up grub-efi-amd64-signed (1.167~18.04.1+2.04-1ubuntu44) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
Package grub-efi-arm64-signed is not installed.
---
Is this supposed to be safe to install on non-EFI systems?
** Affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
** Package changed: shim-signed (Ubuntu) => grub2-signed (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1931518
Title:
grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI
install
Status in grub2-signed package in Ubuntu:
New
Bug description:
On our hosts we are seeing
---
$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up grub-efi-amd64-signed (1.167~18.04.1+2.04-1ubuntu44) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
Package grub-efi-arm64-signed is not installed.
dpkg: error processing package shim-signed (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
---
Indeed grub-install as called is failing
---
$ sudo grub-install --target=x86_64-efi --auto-nvram
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
---
This is a VM that is not booting via EFI
I feel pretty sure this has come in via
http://launchpadlibrarian.net/541948832/grub2-signed_1.167~18.04.1_1.167~18.04.3.diff.gz
* key on grub-efi-$(DEB_HOST_ARCH) as the binary package for
download-signed since grub-efi-* and grub2-common are now built from
separate sources.
This seemed to come in via our unatteneded upgrades @
---
Log started: 2021-06-02 06:52:59
files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.9-0ubuntu7.24_all.deb ...
Unpacking python3-apport (2.20.9-0ubuntu7.24) over (2.20.9-0ubuntu7.23) ...
Setting up python3-apport (2.20.9-0ubuntu7.24) ...
Setting up grub-efi-amd64-signed (1.167~18.04.1+2.04-1ubuntu44) ...
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
Package grub-efi-arm64-signed is not installed.
---
Is this supposed to be safe to install on non-EFI systems?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1931518/+subscriptions
More information about the foundations-bugs
mailing list