Dear Tumbleweed users, Last weekend i updated my Tumbleweed system (as i do almost every day using zypper dup). On the next reboot i discovered that the new GRUB2-theme which i had designed just the week before was gone and had been replaced by the standard openSUSE-theme. I ran rpmconfigcheck which showed nothing related to GRUB. So i checked /etc/default and found that there was a file grub.old and in /etc/default/grub the reference to my private GRUB2-theme had been replaced by a reference to the openSUSE-theme. I undid that change, ran grub2-mkconfig and restarted my system. Still my GRUB2-theme did not show up. A look in /boot/grub2/themes revealed that my GRUB2-theme was gone (deleted!). Checking bugzilla i found this: https://bugzilla.opensuse.org/show_bug.cgi?id=1191251 However up to now nobody cared about this bugreport so i decided to place this message here as a warning to all of you. Regards Hagen
Op vrijdag 8 oktober 2021 13:34:29 CEST schreef Hagen Buliwyf:
I suspect the culprit is in this .spec file. https://build.opensuse.org/package/view_file/Base:System/branding-openSUSE/ branding-openSUSE.spec?expand=1 -- fr.gr. member openSUSE Freek de Kruijf
On Fri, Oct 08, 2021 at 01:34:29PM +0200, Hagen Buliwyf wrote:
It seems that /usr/share/grub2/themes/openSUSE/activate-theme is responsible. -- ============================ Roger Whittaker roger@disruptive.org.uk https://notes.smuvelious.org ============================
On 2021-10-08 11:15 a.m., Roger Whittaker wrote: I love your song! ;-) https://www.youtube.com/watch?v=sGWs1HK8iDU
On 08.10.2021 18:15, Roger Whittaker wrote:
Yes. It should not remove the whole /boot/grub2/themes, but just /boot/grub2/themes/openSUSE. More precise system "rm -rf $grub2_theme_dir/$theme"; As for replacing current theme - well, this script is called "activate-theme" and it does exactly that. Package postinstall should probably check on update what theme is currently configured. This may need additional flag to activate-theme script to distinguish between "update files" and "update files and activate".
Op vrijdag 8 oktober 2021 13:34:29 CEST schreef Hagen Buliwyf:
I suspect the culprit is in this .spec file. https://build.opensuse.org/package/view_file/Base:System/branding-openSUSE/ branding-openSUSE.spec?expand=1 -- fr.gr. member openSUSE Freek de Kruijf
On Fri, Oct 08, 2021 at 01:34:29PM +0200, Hagen Buliwyf wrote:
It seems that /usr/share/grub2/themes/openSUSE/activate-theme is responsible. -- ============================ Roger Whittaker roger@disruptive.org.uk https://notes.smuvelious.org ============================
On 2021-10-08 11:15 a.m., Roger Whittaker wrote: I love your song! ;-) https://www.youtube.com/watch?v=sGWs1HK8iDU
On 08.10.2021 18:15, Roger Whittaker wrote:
Yes. It should not remove the whole /boot/grub2/themes, but just /boot/grub2/themes/openSUSE. More precise system "rm -rf $grub2_theme_dir/$theme"; As for replacing current theme - well, this script is called "activate-theme" and it does exactly that. Package postinstall should probably check on update what theme is currently configured. This may need additional flag to activate-theme script to distinguish between "update files" and "update files and activate".
participants (5)
-
Andrei Borzenkov -
Freek de Kruijf -
Hagen Buliwyf -
James Knott -
Roger Whittaker