Your message dated Wed, 11 Feb 2026 14:03:25 +0000
with message-id <[email protected]>
and subject line 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
has caused the Debian Bug report #1127652,
regarding grub-efi-amd64-signed: Booting grub is impossible on 2.14 version
with "failed to install protocols" and "cannot load image" errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1127652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127652
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-efi-amd64-unsigned
Version: 1+2.12+9
Severity: important
X-Debbugs-Cc: [email protected]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
I have upgraded to 2.14 on Experimental, but booting does not work at all.
Errors such as:
```
error: ../../../grub-core/loader/efi/linux.c:437:failed to install protocols
```
and
```
error: ../../../grub-core/loader/efi/linux.c:227:cannot load image
```
occur, and these prevent any progression. I since then have downgraded to
2.12.9 on Trixie, which fixes the issue.
I wonder if this affects others who upgraded to 2.14.
One thing I need to mention is that I installed the 2.14 version to test out
the argon2id addition and switched the key to argon2id with `cryptsetup
luksConvertKey`. Before the downgrade, I switched back to the old pbkdf2.
- -- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.19-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages grub-efi-amd64-signed depends on:
ii grub-common 2.12-9
Versions of packages grub-efi-amd64-signed recommends:
ii shim-signed 1.47+15.8-1
grub-efi-amd64-signed suggests no packages.
Versions of packages grub-efi-amd64-unsigned depends on:
ii grub-common 2.12-9
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQTsigbt7ZnibbpjLSwmygukCVXDVgUCaYwwMwAKCRAmygukCVXD
VoqSAQD0+PeYSPpGYq9IYzG2Ow6VMx/VMz6xBOxgV6R2cPmSnQD+NtEVs2B6XIEh
M/YI8C4voUl1KDptXM0/+bbQKnJubgs=
=9A5e
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Wed, Feb 11, 2026 at 01:39:39PM +0000, Mate Kukri wrote:
>With Secure Boot enabled, and if you are generating your own GRUB
>image, with a manual grub-install invocation, you must include the
>"peimage" module. This is included with the default setup installed by
>the packaging.
Hence closing this bug.
GRUB is working fine; in your initial report you didn't even tell us
some of the information that was critical: you're building your own
grub image, doing your own signing etc. Please think about the time of
maintainers in the future.
--
Steve McIntyre, Cambridge, UK. [email protected]
Who needs computer imagery when you've got Brian Blessed?
--- End Message ---
