Description of problem: After uninstalling sugar-logos, the Sugar boot splash imagery remains on the system. Version-Release number of selected component (if applicable): 3.fc13 How reproducible: Always. Steps to Reproduce: 1. yum install sugar-logos 2. yum remove sugar-logos 3. Reboot the machine Actual results: The Sugar boot splash screen still displays on boot. Expected results: The default boot splash screen ("charge" on Fedora 13) should display on boot. Additional info: When installing sugar-logos, the following error comes up: Non-fatal POSTIN scriptlet failure in rpm package sugar-logos-3-3.fc13.noarch warning: %post(sugar-logos-3-3.fc13.noarch) scriptlet failed, exit status 1 However, no error occurs upon removal of the package.
I think this is a behaviour all plymouth themes share, since one has to rebuild the initrd afterwards. I'm not entirely sure why this isn't happening as part of the RPM remove process, though. plymouth-set-default-theme supports a trigger called --rebuild-initrd which you'd have to use.
Does the use of --rebuild-initrd or a call of dracut solve this for you?
Yes; I ran dracut a few days ago to build a new initrd (for an unrelated matter), and now the splash screens are back to the Fedora default. So it appears rebuilding the initrd fixes it.
The plymouth folks say this happens for a reason, since we don't want to randomly rebuild the user's initrd without their permission. I'd rather have us follow them on this decision, but I hear that there might be a way for this to work better in F14, because plymouth might get its own initrd. I'm closing this for now. Thanks for the report, though!