Your message dated Fri, 2 Apr 2021 21:42:20 +0300 with message-id <20210402184220.kovzoslpqb6tjarz@acr13.nuvreauspam> and subject line Re: Bug#986298: 2.02+dfsg1-20+deb10u4: kernel boot fail. has caused the Debian Bug report #986298, regarding 2.02+dfsg1-20+deb10u4: kernel boot fail. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: 2.02+dfsg1-20+deb10u4 Version: 2.02+dfsg1-20+deb10u4 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'), (102, 'experimental'), (50, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-16-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled * Install / update to grub-common grub-pc grub-pc-bin grub2 grub2-common - version: 2.02+dfsg1-20+deb10u4 * Install 2.02+dfsg1-20+deb10u3 - system works again * can not boot: ... grub_register_command_lockdown not found ... * boot system
--- End Message ---
--- Begin Message ---On Vi, 02 apr 21, 18:15:02, Stefan Nitz wrote: > Package: 2.02+dfsg1-20+deb10u4 > Version: 2.02+dfsg1-20+deb10u4 > Severity: critical > Justification: breaks the whole system [...] > * Install / update to grub-common grub-pc grub-pc-bin grub2 grub2-common - > version: 2.02+dfsg1-20+deb10u4 > * Install 2.02+dfsg1-20+deb10u3 - system works again > * can not boot: ... grub_register_command_lockdown not found ... > * boot system Hello, This report was reported against an inexistent package. Normally I would just reassign to the correct one, however there is a lot of information missing that could be necessary to find the issue. Please make a new report by running reportbug grub2 Kind regards, Andrei -- Looking after bugs assigned to unknown or inexistent packages
signature.asc
Description: PGP signature
--- End Message ---
