On 05/12/2022 18:33, Steve McIntyre wrote:
On Mon, Dec 05, 2022 at 06:19:53PM +0100, Eric Valette wrote:
On 05/12/2022 18:07, Steve McIntyre wrote:
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.
On Mon, Dec 05, 2022 at 06:19:53PM +0100, Eric Valette wrote:
>On 05/12/2022 18:07, Steve McIntyre wrote:
>
>> 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
On 05/12/2022 18:07, Steve McIntyre wrote:
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
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
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
5 matches
Mail list logo
