Bug#1127652: closed by Steve McIntyre <steve at einval.com> (Re: Bug#1127652: grub-efi-amd64-signed: Booting grub is impossible on 2.14 version with "failed to install protocols" and "cannot load image" errors)
horsey_guy
horsey_guy at proton.me
Sat Feb 14 05:12:37 GMT 2026
Apologies for the rushed bug report.
When I experienced these errors, I have installed grub2.14 (upgrading `grub-efi-amd64-unsigned`, `grub-efi-amd64-signed`, `grub2-common`, `grub-common`, & `grub-efi-amd64-bin`) from the Debian Sid repositories, which are already signed. Grub was not self-built nor self-signed.
What's peculiar is that I tried upgrading to grub2.14 again from the Debian repositories (executing `grub-install` and `update-grub` again), but the same error messages occurred on the second attempt.
Downgrading to grub2.12 works as normal.
So please reopen this bug report as I believe this could be a legitimate bug with grub2.14.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - horsey_guy at proton.me - 0xEC8A06ED.asc
Type: application/pgp-keys
Size: 840 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20260214/6f062aeb/attachment.asc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 343 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20260214/6f062aeb/attachment.sig>
More information about the Pkg-grub-devel
mailing list