Package: grub-efi-amd64-signed Version: 1+2.02+dfsg1+6 Severity: critical Justification: makes the system completely unbootable
When grub-efi-amd64-signed is installed and /boot is on an encrypted file system and GRUB_ENABLE_CRYPTODISK=y is present in /etc/default/grub, the system fails to boot, since cryptodisk appears to be missing from the installed image. Removing grub-efi-amd64-signed works around the problem, since it then seems to use a locally built image? I suspect just adding cryptodisk to GRUB_MODULES in grub's debian/build-efi-images would be sufficient to make this work correctly. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=nb_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
