Issue with Grub-customizer [Issue - stuck on kernel loading]

Ask Fedora
, ,
1

My problem is when I needed to shutdown manually my laptop through its power button when I’m stuck at the loading kernel version. I notice it happens when I update to newer kernels and updated to F41.

I don’t know if this was cause by the grub-customizer. I found some fix from this same issue. Where I needed to reinstall the grub configurations

Also, I run these commands from this output based on this discussion to check any issues while having a grub-customizer.

I get this output

sudo rpm -qf /etc/grub.d/*

error: file /etc/grub.d/*: No such file or directory

sudo rpm -V grub2-tools

missing   c /etc/grub.d/10_linux
missing   c /etc/grub.d/10_reset_boot_success
missing   c /etc/grub.d/12_menu_auto_hide
missing   c /etc/grub.d/14_menu_show_once
missing   c /etc/grub.d/20_linux_xen
missing   c /etc/grub.d/20_ppc_terminfo
missing   c /etc/grub.d/30_uefi-firmware
missing   c /etc/grub.d/40_custom
missing   c /etc/grub.d/41_custom

Should I remove the grub-customizer? and just used the default grub file? or Am I missing something based on the output from above?

Thanks for some help, still quite a newbie.

2

Added f41, gnome, grub

3

There are several reports with grub-customizer breaking setups on Fedora machines. Better remove it and restore the default config if possible.

3 Likes
4

Some of us have tried to get grub-customizer removed from the repos for a while now, since it’s not compatible with Fedora and can really mess up your system. Unfortunately the maintainers haven’t decided to remove it as of yet.

https://bugzilla.redhat.com/show_bug.cgi?id=2257127

4 Likes
5

The biggest problem with grub-customizer is that it renames the files in /etc/grub.d. This will become a problem the next time grub2 gets updated, as the files from the grub2 will be restored to /etc/grub.d, and you will get duplicate files with identical contents. Then when you rebuild grub.cfg, you get a real messed up configuration files due to duplicated sequences in the file.

I suspect other distros using grub might have the same problem.

1 Like
6

I am surprised package maintainers have the freedom not to retire a package that obviously does harm to the distro. Can’t fesco force retirement of the package?

1 Like
7

Added boot and removed gnome

8

I agree. The primary maintainer @vascom hasn’t responded after 10 months of the ticket being up with the ‘Urgent’ status, but they keep building new packages:

https://koji.fedoraproject.org/koji/packageinfo?packageID=18277
https://bodhi.fedoraproject.org/updates/FEDORA-2024-75c49b7e1a

Perhaps they somehow missed the ticket completely and would need to be emailed directly about it.

2 Likes
9

Thanks for all the inputs and insights folks! We’ll remove the grub-customizer.

10

Update: After I removed the grub-customizer by doing using the remove command and generated a new grub file. I have now a problem where the grub options won’t show up for dual booting on windows and it directly boot into the latest kernel of Fedora.

I think the grub-customizer messed up with my system.

Any thoughts? @tqcharm @litemotiv @vekruse @augenauf

11

Does running

$ sudo rpm -V grub2-tools

still report those missing files in /etc/grub.d? If that’s the case then you need to reinstall them:

$ sudo dnf reinstall grub2-tools

after that you need to regenerate grub:

$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
2 Likes
12

Alright, I found out that there are still missing files:

missing   c /etc/grub.d/01_users
missing   c /etc/grub.d/10_linux
missing   c /etc/grub.d/10_reset_boot_success
missing   c /etc/grub.d/12_menu_auto_hide
missing   c /etc/grub.d/14_menu_show_once
missing   c /etc/grub.d/20_linux_xen
missing   c /etc/grub.d/20_ppc_terminfo
missing   c /etc/grub.d/25_bli
missing   c /etc/grub.d/30_uefi-firmware
missing   c /etc/grub.d/40_custom
missing   c /etc/grub.d/41_custom

Even if I found a solution from the fedora subreddit. Doing
sudo grub2-editenv - unset menu_auto_hide. Then updating the grub.

I reinstall the grub2-tools. Yet there’s a warning on the reinstalling page of fedora documentation, saying "

Do not use the grub2-install command on UEFI systems. On those systems, bootloaders are in the shim and grub-efi RPM packages. By reinstalling those packages, the bootloaders are reinstalled to their proper location in /boot/efi/ on the EFI System volume."

Any insights?

Edit: this works, even if I have those missing files earlier. Yet, I still follow to reinstall the grub2-tools. And whenever I enter the sudo rpm -V grub2-tools, I got blank output. I think that resolves/added the missing files.

Thanks @litemotiv!

1 Like