On Mon, Dec 05, 2022 at 05:55:13PM +0100, Eric Valette wrote: >I had the previous version 2.06-5 on a laptop, and it was not affected by the >bug, Only my very old Desktop was. > >As the bug was closed, I did install 2.06-6 on my laptop (or at least the >composant actually upgraded) and now it also fails on my laptop with same >error than on my desktop. > >I now have apparently several grub version flavors and several shim version >flavor: > >15.4 for shim-signed:amd64 and shim-signed-common and 15.6 for >shim-helpers-amd64-signed and shim-unsigned > >And for grub, I have 2.06-6 except for the important part : >grub-efi-amd64-signed that is still at 2.06-5.
The shim versions don't matter here, the issues are all in grub. >root@xxxx:~# dpkg -l grub* >Desired=Unknown/Install/Remove/Purge/Hold >| >Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend >|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) >||/ Name Version Architecture Description >+++-=====================-============-============-================================================================= ... >hi grub-efi-amd64-signed 1+2.06+5 amd64 GRand Unified Bootloader, >version 2 (amd64 UEFI signed by Debian) You're using the Secure Boot path (shim -> grub-efi-amd64-signed), so the version of grub that matters for you is the signed version: 1+2.06+5. That is (so far) still based on grub2 source version 2.06-5. It takes a short while for the builds to propagate through the signing machinery in Debian. Please be patient, the fix is on the way to you. If you can check again when 1+2.06+6 is available, that will be more helpful. -- Steve McIntyre, Cambridge, UK. st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier