version_find_latest has been removed from GRUB but grub-customizer still relies on it

Bug #1992200 reported by Vladimir Garistov
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Grub Customizer
New
Undecided
Unassigned

Bug Description

When I launch grub-customizer it throws the following error (see attachment): /etc/grub.d/proxifiedScripts/linux: line 198: version_find_latest: command not found

According to https://git.savannah.gnu.org/cgit/grub.git/commit/util/grub-mkconfig_lib.in?id=a79c567f6b5820a8795c273a9eaabd06a1f92b29 the function version_find_latest has been removed from GRUB.

OS: Arch Linux x86_64
Kernel: 5.15.71-1-lts
grub-customizer version: 5.2.2

Revision history for this message
Vladimir Garistov (cartogan) wrote :
Revision history for this message
Daniel Richter (danielrichter2007) wrote :

This is a problem of the script update mechanism. The file /etc/grub.d/proxifiedScripts/linux is moved from /etc/grub.d/10_linux after saving any modifications the first time. When updating grub, there's a new file created at the original location (/etc/grub.d/10_linux). Grub Customizer generally detects this problem and cleans up to avoid duplicates, but cannot handle files that became incompatible. That's the bug to fix.

Here's your workaround:

sudo mv /etc/grub.d/10_linux /etc/grub.d/proxifiedScripts/linux

Revision history for this message
Vladimir Garistov (cartogan) wrote :

Thank you, this did solve my issue.
I would just like to add that it took me a while to identify what the problem is because the error window that I attached a screenshot of used to be taller than my monitor and cluttered with a ton of harmless LVM warnings. The actually important error message was outside the monitor and I was able to read it only after exporting LVM_SUPPRESS_FD_WARNINGS. I can't reproduce it now that grub-customizer starts normally but I thought it's something worth mentioning.

Revision history for this message
ROSET Nathan (nathroset97) wrote :

Hello,
I was also affected by this bug after upgrading from Kubuntu 23.04 to 23.10, however thanks to your workaround I was able to solve the issue as well. This comment is simply to signal that the bug is still present in version 5.2.4

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.