Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#75002 - [grub] secure boot broken with grub 2.06.r261.g2f4430cc0-1

Attached to Project: Arch Linux
Opened by sunghwan jung (sunghwan) - Thursday, 09 June 2022, 05:35 GMT
Last edited by David Thurstenson (thurstylark) - Friday, 08 July 2022, 01:57 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned   Reopened
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 4
Private No

Details

Description:
after update to 2.06.r261.g2f4430cc0-1, secure boot is not work with "error: prohibited by secure boot policy
enter entering rescue mode
grub rescue>".
secure boot is work again after downgrade to 2.06-5.

Additional info:
* grub 2.06.r261.g2f4430cc0-1
* kernel 5.18.2-arch1-1
* secure boot by shim with shim-signed package (https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#shim)
* partiton - nvmen0n1p1:efi,vfat nvmen0n1p2: windows reserved partiton nvmen0n1p3:windows11,ntfs nvmen0n1p4:arch,ext4
This task depends upon

Comment by sunghwan jung (sunghwan) - Thursday, 09 June 2022, 06:32 GMT
it may be related to https://git.savannah.gnu.org/cgit/grub.git/commit/?id=6fe755c5c07bb386fda58306bfd19e4a1c974c53
Comment by Morten Linderud (Foxboron) - Thursday, 09 June 2022, 07:08 GMT
You need the signed 15.6 shim, it's currently working as expected.
Comment by Lyubomir (mystiquewolf) - Friday, 08 July 2022, 01:57 GMT
  • Field changed: Percent Complete (100% → 0%)
FWIW this bug still happens after I updated both shim-signed to 15.6 and grub. With previous version of shim-signed 15.4,the issue still happened after update of grub. Reverting grub to 2.06-5 back then fixed it, so I have some reason to believe that the grub update is the cause of it.

Loading...