[Bug 908451] New: GRUB update removes custom themes
http://bugzilla.opensuse.org/show_bug.cgi?id=908451 Bug ID: 908451 Summary: GRUB update removes custom themes Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: jon@grossart.net QA Contact: jsrain@suse.com Found By: --- Blocker: --- 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 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908451 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jon@grossart.net, | |jsrain@suse.com Assignee|jsrain@suse.com |mchang@suse.com Flags| |needinfo?(jon@grossart.net) --- Comment #1 from Jiri Srain <jsrain@suse.com> --- Can you check that after step 2 the theme is set correctly in /etc/default/grub? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908451 Jon Grossart <jon@grossart.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jon@grossart.net) | --- Comment #2 from Jon Grossart <jon@grossart.net> --- /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 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908451 --- Comment #3 from Jon Grossart <jon@grossart.net> --- unconditionally updating grub2-branding-openSUSE recreated the behavior -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908451 http://bugzilla.opensuse.org/show_bug.cgi?id=908451#c4 Tony Pott <tony.pott@ntlworld.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tony.pott@ntlworld.com --- Comment #4 from Tony Pott <tony.pott@ntlworld.com> --- 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? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908451 http://bugzilla.opensuse.org/show_bug.cgi?id=908451#c5 simon izor <simonizor@protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simonizor@protonmail.com Severity|Normal |Major --- Comment #5 from simon izor <simonizor@protonmail.com> --- 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 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908451 http://bugzilla.opensuse.org/show_bug.cgi?id=908451#c6 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt@suse.com Resolution|--- |INVALID --- Comment #6 from Fabian Vogt <fvogt@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com