https://bugzilla.novell.com/show_bug.cgi?id=757683
https://bugzilla.novell.com/show_bug.cgi?id=757683#c35
--- Comment #35 from Michael Chang
After looking at it the way to go is using a theme for gfxmenu, not just a background image. Otherwise it just looks dead ugly (IMHO). The changes required a quite minimal. Or rather, nothing needs to be changed as you can point to a non-existing theme file and grub-mkconfig works just fine.
I agree with you. We could add theme support on yast and perl bootloader. It's safe and wouldn't break anything if required themes are missing. Then the ball passed to art work and the branding package .. (maybe we refer to comment#26(thanks Atri) based on starfield and replace the images with openSUSE ..)
The grub2 branding package could even have both background images and theme files as typically the theme will have some background image as well.
Agree and I think my plan is like yours ..
My suggestion would be to rename the branding package to simply grub2-branding-openSUSE which has background images in
/boot/grub2/backgrounds/openSUSE/
and a theme in
/boot/grub2/themes/openSUSE/
This way you can install several themes in parallel.
This is good idea.
Also, the package would need a post-install script that adds/modifies these two entries to /etc/default/grub:
GRUB_BACKGROUND=/boot/grub2/backgrounds/openSUSE/1024x768.png GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt
and has to run grub2-mkconfig to update the config file and activate the theme.
There are a few problems with this, though:
a) using symlinks to link common image resolutions is probably not a good idea as UEFI requires vfat for the boot partition which does not support symlinks
Good catch .. well I'm sorry about not perceive the issue ahead.
b) grub2-mkconfig might be a bit overkill for a post-script in our branding packages
I would like to avoid it as well and the idea is config entries should be modified by yast when possible. This is why in propose() a presumed background (/boot/grub2/backgrounds/default-<resolution>.png) is used in looking up them. However the shortage is not reliable when branding packages changes their images file's location. :( I am not much oppose to call grub2-mkconfig in branding package if maintainer thinks it's fine.
c) yast2 currently writes /boot/grub2/backgrounds/default-<resolution>.png into the grub2 config which is theme independent; as we can't simply use symlinks for a 'default' theme due to a) yast2 has to know the active branding name (maybe looking at /etc/default/grub)
I suppose we could fix by renaming to sth like "/boot/grub2/backgrounds/openSUSE/<resolution>.png" ?
Independent of the above our grub2 setup references a font file in /usr/share/grub2 which should better be in /boot/grub2 somewhere.
My first thought is to look at grub2-install to copy those font files together with *.mod and modify the grub.d/ scripts to search font files in new locations. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.