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

Package: grub-pc Version: 2.02+dfsg1-20+deb10u4 Followup-For: Bug #984426 Hi, just to inform that I suffered this problem too, after upgrading my system to Debian 10.9 (in the last security upgrade several days ago). I agree that the problem arose due to a misconfiguration in my system, as my

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

Package: grub-pc Version: 2.02+dfsg1-20+deb10u4 Followup-For: Bug #984426 Hello, I experienced the same problem on a couple of my machines too. Yes, technically a misconfiguration at my end, but the number of me-too's suggests that there are many others not realising that debconf needs to know

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

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?

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

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? Marco -- codecivil Dr. Marco Kühnel ICT Services, Vechteweg 4,

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

On Wed, Mar 03, 2021 at 06:24:30PM +0100, Karsten wrote: > Am 03.03.21 um 18:00 schrieb Colin Watson: > > Since you're reporting this against grub-pc 2.02+dfsg1-20+deb10u4, and > > since the mentioned grub_register_command_lockdown symbol was only > > introduced in that version, then there must

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

Am 03.03.21 um 18:00 schrieb Colin Watson: > On Wed, Mar 03, 2021 at 05:20:39PM +0100, Karsten wrote: >> there was no system update or an installation. It booted perfect. > Since you're reporting this against grub-pc 2.02+dfsg1-20+deb10u4, and > since the mentioned grub_register_command_lockdown

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

On Wed, Mar 03, 2021 at 05:20:39PM +0100, Karsten wrote: > there was no system update or an installation. It booted perfect. Since you're reporting this against grub-pc 2.02+dfsg1-20+deb10u4, and since the mentioned grub_register_command_lockdown symbol was only introduced in that version, then