As pointed out in 14864, updating mageia-theme-Default (which calls among others /usr/share/bootsplash/scripts/switch_themes Mageia-Default in its %posttrans) should rebuild the initrd.
Barry experienced that it's necessary at least for grub2 users (I did not need to do so here on a system with grub legacy).
Currently in its "update" function switch_themes calls:
if [[ -z $update ]]; then
/usr/sbin/plymouth-set-default-theme has a --rebuild-initrd switch:
-R, --rebuild-initrd Rebuild initrd (necessary after changing theme)
Adding this switch to the switch_themes instruction should do the trick.
Steps to Reproduce:
CC'ing shlomi who is the maintainer of bootsplash. WDYT?
(In reply to Rémi Verschelde from comment #1)
> CC'ing shlomi who is the maintainer of bootsplash. WDYT?
no idea about that - I just adopted bootsplash because it was an orphan and I'm not knowledgeable about it. If you want, I can revoke my maintainer status of it.
-- Shlomi Fish
CCing Thomas as he has been looking at a similar issue in Bug15486
Adding to the Mageia 6 tracker so that we don't forget about it (though the whole theme scripts should probably be completely reworked for Mageia 6, thus obsoleting this report).
Rémi, is this worth an ERRATA entry?
I think so, at least if installing a custom theme (e.g. plymouth-theme-glow) does not trigger a rebuild of the initrd. I'll try that to confirm.
Actually no, custom plymouth themes do trigger a rebuild of the initrd when installed. It's only if you update mageia-theme-Default that no rebuild is done, so it shouldn't affect Mageia 5 users (unless we provide an update to mageia-theme and forget about this bug).
MGA5TOO FOR_ERRATA =>
(In reply to Rémi Verschelde from comment #4)
> Adding to the Mageia 6 tracker so that we don't forget about it (though the
> whole theme scripts should probably be completely reworked for Mageia 6,
> thus obsoleting this report).
And? Did the scripts get reworked, too?
Not that I know of, but it's not critical for Mageia 6 as long as the initrd is properly rebuilt for the new theme before making the ISOs.
Assigning to all packagers collectively since Shlomi has no idea how to fix it.
Mageia 6 =>
This should be added, while it's unlikely that an update to Mageia-theme would be shipped, the penalty for having this is small.
Rebuilding the initrd should take too long and while the regularity of kernel updates flush this out to a large degree, it is surely still good form to have the the initrd rebuild to show any theme changes in case we get another Mageia 2 like incident.
If you restrict it to rebuilding current initrd it could be ok.
But its not ok to rebuild all found initrds as it could cause a previous working kernel/initrd to becomu unbootable in case there is some bugs, rendering the recovery processes unusable...