Possible duplicate Memtest proxy rules in GRUB Customizer 5.2.8 on
Ubuntu 26.04.1 LTS
First, thank you to everyone who has contributed to GRUB Customizer. I
appreciate the work that goes into maintaining a tool that makes GRUB
configuration easier to manage, particularly for people running Linux
and Windows side by side.
I encountered an issue with duplicate Memtest entries and have done some
troubleshooting to narrow it down. I'm sharing the findings in the hope
that they help identify an issue in proxy generation or an interaction
with the current Memtest package.
Still not resolved in version 5.2.8
To be clear, used AI to generate this report.
Environment
OS: Ubuntu 26.04.1 LTS (Resolute Raccoon)
GRUB Customizer: 5.2.8-0ubuntu1~ppa1r
GRUB Customizer reported version: 5.2.8
GRUB common: 2.14-2ubuntu2.1
GRUB EFI amd64: 2.14-2ubuntu1
GRUB EFI amd64 bin: 2.14-2ubuntu1
GRUB EFI amd64 signed: 1.215+2.14-2ubuntu1
GRUB 2 common: 2.14-2ubuntu2.1
Memtest86+: 8.00-3
Architecture: x86_64
Boot mode: UEFI
Storage: NVMe
Setup: Ubuntu and Windows Boot Manager
Detected kernels: 7.0.0-38-generic, 6.19.14-061914-generic, 6.17.0-42-generic
Problem
After installing GRUB Customizer 5.2.8, the generated GRUB configuration
initially contained eight Memtest menu-entry definitions across UEFI and
legacy BIOS conditional sections. The entries included 32-bit variants
that appeared inappropriate for this UEFI x86_64 system.
Removing unwanted entries through the GUI did not resolve the issue.
Investigation
The following files were found under /etc/grub.d/:
20_memtest86+_proxy
proxifiedScripts/memtest86+
bin/grubcfg_proxy
backup/etc_grub_d/20_memtest86+
.script_sources.txt
The source mapping contained:
"proxifiedScripts/memtest86+";"20_memtest86+"
The proxy script contained repeated removal rules for the same four
Memtest entry IDs. The original proxy backup contains the following
pattern:
+'Memory test (mt86+x64)'~70f9b3cff2e898bb81cb4d4ba0672667~
+'Memory test (mt86+x64, serial console)'~67bf5be132a8e1e3476cab7b6f51f31a~
-'Memory test (mt86+ia32)'~1bdfaf5b0dfd7d1b6330fabbec29a122~
-'Memory test (mt86+ia32, serial console)'~5d2fc8c7484be835333189aa4de4becd~
-'Memory test (mt86+x64)'~70f9b3cff2e898bb81cb4d4ba0672667~
-'Memory test (mt86+x64, serial console)'~67bf5be132a8e1e3476cab7b6f51f31a~
-'Memory test (mt86+ia32)'~1bdfaf5b0dfd7d1b6330fabbec29a122~
-'Memory test (mt86+ia32, serial console)'~5d2fc8c7484be835333189aa4de4becd~
The same four removal rules appear repeatedly in the original proxy backup.
This seems worth investigating, although I cannot confirm that these rules
alone caused all eight generated definitions.
The original Memtest generator was available in the GRUB Customizer
backup directory. Restoring it and disabling the proxy did not, by
itself, reduce the generated configuration's eight Memtest definitions.
The system was confirmed to be booted in UEFI mode. The EFI
configuration at /boot/efi/EFI/ubuntu/grub.cfg contains:
search.fs_uuid b028ad2f-6c0d-480b-99a4-9793e5532386 root
set prefix=($root)'/grub'
configfile $prefix/grub.cfg
This points to the main configuration at /boot/grub/grub.cfg.
Workaround and current state
I temporarily disabled the standard Memtest generator and created a
custom /etc/grub.d/20_memtest86+ script that generates a single 64-bit
UEFI Memtest entry.
After running sudo update-grub, the generated configuration contained
exactly one Memtest entry:
menuentry "Memory test (Memtest86+, UEFI)" --class memtest {
The current diagnostic output confirms that the entry is at line 273 of
/boot/grub/grub.cfg.
The following command completed without errors:
grub-script-check /boot/grub/grub.cfg
Exit status: 0.
The current configuration also contains Ubuntu kernel entries for all
three detected kernels and a Windows Boot Manager entry.
The current configuration reflects the workaround; it does not reproduce
the original eight-entry state. I have not yet confirmed the actual
boot-menu appearance after reboot.
Suspected cause
I wonder whether GRUB Customizer 5.2.8 might be mishandling Memtest
proxy-script generation or entry bookkeeping, resulting in repeated
rules or duplicate definitions.
I realize that the standard Memtest generator contains both UEFI and
legacy BIOS conditional sections, and that definitions in those sections
do not necessarily all appear in the active boot menu. The precise
origin of the original duplicates therefore remains unconfirmed.
It is also possible that an interaction with the installed Memtest
package or another part of the GRUB generation process contributes to
the behavior.
Requested investigation
Could the maintainers help determine whether the repeated proxy rules
are expected, and whether the proxy-generation logic can produce
duplicate Memtest definitions in this environment?
I would be happy to perform further tests if they would help establish a
reliable reproduction.
Thank you again for your time and for maintaining GRUB Customizer. I
appreciate the effort involved in supporting different distributions,
boot modes, and configurations, and I hope these findings are useful.
One clarification about the repeated removal rules in the proxy script:
these may have accumulated as a result of my attempts to remove the
duplicate Memtest entries through GRUB Customizer after the problem
first appeared. I therefore cannot confirm that the repeated rules were
present in the original proxy before I started troubleshooting.
The original issue remains that the generated GRUB configuration
contained eight Memtest menu-entry definitions, and removing entries
through the GUI did not resolve the problem. Restoring the original
Memtest generator and disabling the proxy also did not immediately
eliminate the duplicates.
I eventually installed a custom Memtest generator that produces a single
64-bit UEFI entry. The resulting configuration passes grub-script-check,
and Ubuntu and Windows Boot Manager entries remain present.
I haven't yet reproduced the issue from a clean configuration, so I
can't confirm whether the root cause lies in proxy generation, entry
deletion/bookkeeping, or an interaction with the Memtest package. I hope
these findings are useful in investigating it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2128709
Title:
Grub Customizer fails to remove or clean up Memtest86+ proxy scripts
upon entry deletion, resulting in malformed grub.cfg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/grub-customizer/+bug/2128709/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
