Package: grub-common Version: 2.02~beta2-36 Severity: important --- Please enter the report below this line. ---
grub creates rescue entries for all found Linux kernels. However the kernel parameters do not include noresume. Hibernate/Resume is traditionally an issue on Linux. Crashes on resume are a common problem. To be able to use the computer again, the user needs to boot without resuming from a RAM image in such a sitation. This require the kernel parameter noresume. Which the user most likely doesn't know about, so the user needs another computer to be able to look it up. Effectively the user may be locked out of the system for a long time. Adding the noresume parameter to the rescue entry would make rescue a viable option for getting a system back into a useable state (and IMO more closely match user expectations). A rescue entry that tries to resume from a RAM image, if one is found, seems broken to me. Philipp --- System information. --- Architecture: amd64 Kernel: Linux 4.6.0-rc5-amd64 Debian Release: stretch/sid 500 unstable ftp.de.debian.org 500 testing ftp.de.debian.org 1 experimental ftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===============================================-+-========================= libc6 (>= 2.3) | libdevmapper1.02.1 (>= 2:1.02.36) | libfreetype6 (>= 2.2.1) | libfuse2 (>= 2.8.4-1.4) | liblzma5 (>= 5.1.1alpha+20120614) | libpng12-0 (>= 1.2.13-4) | zlib1g (>= 1:1.1.4) | gettext-base | Recommends (Version) | Installed =========================-+-=========== os-prober (>= 1.33) | 1.71 Suggests (Version) | Installed =================================-+-================ multiboot-doc | grub-emu | xorriso (>= 0.5.6.pl00) | desktop-base (>= 4.0.6) | 8.0.2 console-setup | 1.142 -8<---8<---8<---8<---8<---8<---8<---8<---8<-- Please attach the file: /tmp/reportbug-ng-grub-common-LU0Tym.txt to the mail. I'd do it myself if the output wasn't too long to handle. Thank you! ->8--->8--->8--->8--->8--->8--->8--->8--->8--