Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"

Colin Watson cjwatson at debian.org
Thu Mar 4 10:20:14 GMT 2021


On Thu, Mar 04, 2021 at 10:43:27AM +0100, Marco Kühnel wrote:
> I have the same error message after the update to grub2/2.02+dfsg1-
> 20+deb10u4, but with grub-efi-amd64* instead of grub-pc. After pressing
> the "arbitrary key", Debian boots but fails to start lightdm. Should I
> report a new bug?

Anything involving UEFI is distinct from this bug, so please report it
separately with full details.

-- 
Colin Watson (he/him)                              [cjwatson at debian.org]



More information about the Pkg-grub-devel mailing list