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

[Jose Antonio Jimenez Madrid]

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 main HDD was broken several months ago, so I "cloned" the system
onto the new HDD, but
I installed grub manually onto the new HDD, but I forgot to update
debconf. The last time I replaced a HDD was 15 years ago, when LILO was
the boot loader, so I did not take into account debconf for grub, my
mistake.
Anyway, in the upgrade process, I suggest to show a warning like other
packages do (as example when a different version of kernel is running
not corresponding to the driver version you are installing) to
prevent to have an "inaccessible" system.
If needed, I can open a new bug, with severity "wish list" to request
this feature or to keep this bug open until the warning is implemented,
so if other people have the same problem can fix it quickly.

Thank you for your great work.

Sincerely,

Jose