Grub conflicts with grub-customizer

[michaldybczak]

@wongs

You can copy/back up those folder / files into …/grub.d.old instead of deleting them.

The grub background can be set by editing as root the text file in /etc/default/grub.

You should see one of the lines as
GRUB_BACKGROUND = “path to file”

Change the path to the correct location , keep the quotation marks.

After you remove GC, you can do a sudo update-grub.

Doesn’t work .
When doing sudo-update-grub I get the same error as someone from above:

@sage

Generating grub configuration file ...
Script `/boot/grub/grub.cfg.new' contains no commands and will do nothing
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.

and the /etc/grub.d/ is not populated with configs.

This is disappointing because there should be a huge announcement with info how to properly remove grub-customizer configs so it would all work well after the update. But:

• there was no warning that this happens, just one day, we have to remove grub-customizer, and then you are left alone
• no alternative software was presented
• no documentation how to deal with after-grub-customizer systems.
• no clear solution anywhere how to deal with duplicated entries

So the “SOLUTION” simply broke user space in order to fix it… Good job Manajro…
However, it probably resulted from lack of imagination of what the consequences are for the users who used grub-customizer FOR YEARS! From my standpoint, it was fine before, now in order to fix an issue that was not-issue for me, I landed with an issue… It is possible that with some wild and massive GRUB customizations done by grub-customizer it had a potential to cause issues during updates, but most of us, grub-customizer users, did only minor changes, so it never conflicted with updates.