Bug#1102182: efibootmgr: If Secure Boot is enabled, the system may not start after rebooting

To: 1102182@bugs.debian.org
Subject: Bug#1102182: efibootmgr: If Secure Boot is enabled, the system may not start after rebooting
From: Tanaka <debiantanaka45@riseup.net>
Date: Fri, 2 May 2025 00:34:28 +0900
Message-id: <[🔎] 88af9f77-8666-4fbb-9b40-3a1f5b0d6450@riseup.net>
Reply-to: Tanaka <debiantanaka45@riseup.net>, 1102182@bugs.debian.org
References: <174392132724.38851.10382475415261391693.reportbug@tvserver>

Perhaps this /File(\EFI\DEBIAN\GRUBX64.EFI). BO is not installed by Debian, but the firmware of my computer found GRUBX64.EFI in the EFI system partition and added it to the boot entry on its own.

Is it possible to not install grubx64.efi in ESP when using shim?

Reply to:

Follow-Ups:
- Bug#1102182: efibootmgr: If Secure Boot is enabled, the system may not start after rebooting
  - From: Steve McIntyre <steve@einval.com>

Prev by Date: Bug#1102182: (no subject)
Next by Date: Bug#1102182: efibootmgr: If Secure Boot is enabled, the system may not start after rebooting
Previous by thread: Bug#1102182: efibootmgr: If Secure Boot is enabled, the system may not start after rebooting
Next by thread: Bug#1102182: efibootmgr: If Secure Boot is enabled, the system may not start after rebooting
Index(es):
- Date
- Thread