Bug#1100470: grub2-common: Segfault messages when running update-grub
Felix Zielcke
fzielcke at z-51.de
Fri Mar 14 13:22:21 GMT 2025
Am Freitag, dem 14.03.2025 um 10:00 +0100 schrieb eric:
> Package: grub2-common
> Version: 2.12-6
> Severity: normal
>
> Since this update, I have the following worrying messages:
>
> update-grub
> [...]
> Found pcmemtest 64bit EFI image: /boot/pcmemtestx64.efi
Just a side note: pcmemtest is dead upstream and its code has been
integrated into memtest86+ v6.
> Warning: os-prober will be executed to detect other bootable
> partitions.
> Its output will be used to detect bootable binaries on them and
> create new boot entries.
> /usr/lib/os-probes/50mounted-tests: line 72: 6937 Segmentation
> fault (core dumped) grub-mount "$partition" "$tmpmnt" 2>
> /dev/null
> /usr/lib/os-probes/50mounted-tests: line 72: 6973 Segmentation
> fault (core dumped) grub-mount "$partition" "$tmpmnt" 2>
> /dev/null
> /usr/lib/os-probes/50mounted-tests: line 72: 6996 Segmentation
> fault (core dumped) grub-mount "$partition" "$tmpmnt" 2>
> /dev/null
> Found Windows Boot Manager on
> /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
> Adding boot menu entry for UEFI Firmware Settings ...
> done
>
>
Do you have systemd-coredump installed?
Or differently asked: Do you know where it dumped the core on your fs?
Otherwise do this:
Please change the "set -e" at the top of /usr/lib/os-probes/50mounted-
tests after/before to "set -ex", i.e. add x.
And then run update-grub again.
Then it should show the exact invocation of grub-mount which segfaults
More information about the Pkg-grub-devel
mailing list