Bug#908200: grub-efi-*-signed: mismatch between /EFI/vendor (used) and /EFI/debian (expected) when derivative uses unmodified Debian binary packages
Raphaƫl Hertzog
hertzog at debian.org
Fri Sep 7 10:49:43 BST 2018
Source: grub2
Version: 2.02+dfsg1-6
Severity: important
User: devel at kali.org
Usertags: origin-kali
In Kali, UEFI users are no longer able to boot their system:
https://bugs.kali.org/view.php?id=4956
The problem seems to come down to the fact that during initial installation,
(at least) when the install picks the new *-signed packages, they get
installed to /EFI/kali but the binary installed inside is actually
expecting the configuration file in /EFI/debian/grub.cfg.
-- System Information:
Debian Release: buster/sid
APT prefers oldoldstable
APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
More information about the Pkg-grub-devel
mailing list