Bugzilla – Bug 908451
GRUB update removes custom themes
Last modified: 2018-03-11 20:25:06 UTC
I'm using Tumbleweed, and I've seen this happen across multiple installs. 1. create an optional theme in /boot/grub2/themes (not installed via the package manager) 2. set the theme via YaST2 > Boot loader 3. reboot 4. theme shows up 5. have a system update for grub (not sure if just the update grub command will clobber it or if it's a package upgrade) 6. reboot 7. theme is back to the default theme and custom theme has been removed from /boot/grub2/themes
Can you check that after step 2 the theme is set correctly in /etc/default/grub?
/etc/default/grub was updated to point to the correct theme. I did a "zypper dup" from 20141126 to 20141201 and it contained an update that exhibited this behavior. By time the grub2-brandhing-openSUSE package had it's output, it only found the default openSUSE theme and the custom theme was no longer in the directory. Only a few packages were installed before that and only a few had anything related to graphics/boot. The likely culprits are: branding-openSUSE-13.2-10.7 gfxboot-branding-openSUSE-13.2-10.7 grub2-branding-opeenSUSE13.2-10.7
unconditionally updating grub2-branding-openSUSE recreated the behavior
I'm seeing this too (2 years later). I'm happy to work on a fix since the assigned dev hasn't had the chance to do it. This will take a while since I don't currently have a clue where to begin. however, I guess it's not regarded as urgent :-), and is therefore, an ideal task for a newbie to attempt. Can anyone point me to project documentation around package maintenance processes, required testing, patch submission?
This is still a thing. Please look into this. (1/1) Removing grub2-theme-breeze-5.12.3-1.1.noarch ..........................................................[done] Additional rpm output: warning: file /boot/grub2/themes/mkfont.sh: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/unifont-regular-32.pf2: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/unifont-regular-16.pf2: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/unifont-regular-14.pf2: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/unifont-bold-16.pf2: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/theme.txt: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/progress_bar_hl_c.png: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/progress_bar_c.png: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze/progress_bar2_c.png: remove failed: No such file or directory warning: file /boot/grub2/themes/breeze: remove failed: No such file or directory
Themes are not meant to be installed into /boot. They need to be installed into /usr/share/grub2/themes/, where the contained activate-theme script copies the necessary files onto the /boot partition. That this breaks grub2-theme-breeze is a bug in the grub2-theme-breeze package.