Package: shim-signed
Version: 1.50+16.1-2
Followup-For: Bug #1137247
X-Debbugs-Cc: [email protected]

Dear all,

I can confirm exactly the same outcome as Michael's initial report.
Started some days ago after shim-signed upgraded to 1.50, possibly grub was 
already 2.14 or upgraded afterwards.
Lenovo ThinkBook 14 G6 ABP, dual boot with OEM's Windows 11.
UEFI boot order is debian first (which loads grub), Windows second.

1. changing boot order with Windows prevents the issue, Windows boot OK
2. disabling Secure Boot prevents the issue

Tried apt-get --reinstall on all the shim* and grub* packages, did not solve.
Tried resetting to factory default keys in BIOS, and switch between setup and 
regular SB mode, did not solve.

Temporary workaround with SB enabled: power up, F12, override boot order 
selecting Windows instead of debian, boot OK.

Regards
ilGino


-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 7.0.9+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages shim-signed depends on:
ii  debconf [debconf-2.0]      1.5.92
ii  grub-efi-amd64-bin         2.14-2
ii  grub2-common               2.14-2
ii  mokutil                    0.7.2-2
ii  shim-helpers-amd64-signed  1+16.1+2
ii  shim-signed-common         1.50+16.1-2

shim-signed recommends no packages.

shim-signed suggests no packages.

-- debconf information:
  shim-signed/no-valid-sigs:
  shim-signed/revoked-sig:

Reply via email to