Plymouth for brave! If you are fed up with a not working one

Tags: #<Tag:0x00007fe4a17e9220>

Tired of cursing because of plymouth not working?
If you’re brave you can try to downgrade as I and Rugyada made on cooker in vbox.

# rpm -e lib64ply-splash-core4-0.9.3-0.20160305.4-omv2015.0.x86_64 plymouth-plugin-label-0.9.3-0.20160305.4-omv2015.0.x86_64 lib64ply4-0.9.3-0.20160305.4-omv2015.0.x86_64 lib64ply-boot-client4-0.9.3-0.20160305.4-omv2015.0.x86_64 lib64ply-splash-graphics4-0.9.3-0.20160305.4-omv2015.0.x86_64 plymouth-plugin-script-0.9.3-0.20160305.4-omv2015.0.x86_64 plymouth-0.9.3-0.20160305.4-omv2015.0.x86_64 plymouth-scripts-0.9.3-0.20160305.4-omv2015.0.x86_64 plymouth-system-theme-0.9.3-0.20160305.4-omv2015.0.x86_64 --nodeps

# urpmi lib64plymouth2-0.8.9-16-rosa2014.1.x86_64.rpm plymouth-0.8.9-16-rosa2014.1.x86_64.rpm plymouth-plugin-label-0.8.9-16-rosa2014.1.x86_64.rpm plymouth-plugin-script-0.8.9-16-rosa2014.1.x86_64.rpm plymouth-scripts-0.8.9-16-rosa2014.1.x86_64.rpm plymouth-system-theme-0.8.9-16-rosa2014.1.x86_64.rpm

# plymouth-set-default-theme OpenMandriva

# dracut -f

# update-grub2

  • add plymouth in skip.list (/etc/urpmi/skip.list)
  • logout
  • reboot


Please note: There have been cases where it took 1 or 2 more reboot in order to plymouth being properly displayed.

Yes, you read that right :smile:
We used plymouth by ROSA Linux.

1 Like

But it seems to already work in build 130 or am I wrong?

For some it works, for many others doesn’t.
Our plymouth is not working fine since 0.8 > 0.9 upgrade.
Reason for upgrade were that some bugs got fixed according to Plymouth upstream but the fact is that almost all distro didn’t upgrade.
We are speaking of 2 year time now.

And this is not vbox issue… :stuck_out_tongue_closed_eyes:

Of course, rosa-plymouth rpms you can find them in ROSA repository.

No, does not work consistently in 130 or in fully updated Cooker.

Edit: Referring to installations on hardware not in VirtualBox. Though it doesn’t work well there either.

Specifically in Main Updates repo here:

Would perhaps be meaningful if more users/testers could test both on hardware and VBox.:joy:

That being said so far developers have been very resistant to downgrading these packages.:disappointed:

I do not know what to tell you Ben
Some distros have chosen to remain with plymouth <0.9 and it works
Others have chosen to upgrade to version> 0.9 (like mageia 6) and it works

Only oma has a not completely working plymouth.
I only think that is not dependent on vbox, on upstream or on the government :smile:
and that in any case it is possible to fix

If it isn’t impossible to fix then what’s needed is awareness and willingness of developers to fix this. I seem to recall in the past devs either insisting it works when it doesn’t or saying that it isn’t important to them.

I know that it will be noticed by reviewers and will be important to users and worse at this point potential new users.

In summary what’s needed to get developers to become aware that this is a real problem that needs to be fixed? I’m pretty sure bugs have been filed on this haven’t they? Now I need to get a list of unresolved Plymouth bugs…

I think for developers it is just a graphic and aesthetic problem, so insignificant
But developers, often genie in their work, do not have great abilities of attraction towards new users and commercial capacity.

They use “vi” and the console to burn DVDs and they are proud of this.
Proprietary drivers are the devil, firefox shit etc etc

And they would steal users from windows?

IIRC these should be the relevant

I may have missed some though.

Tried in 3 different machines with different versions of Intel graphics. It works in all of them. Before Plymouth would only work occasionally, rarely.



What’s needed now is people testing in as much hw configuration as possible.

Who wants to register to newborn PDT - Plymouth Downgrade Team [1] ? :smile:

[1] Naming credits: @luca