The second command would fail because of the race condition where plymouthd forks and returns, but isn't actually ready to answer connection requests.
The simple fix would be to modify the init script to wait until plymouthd is ready:
/sbin/plymouthd --mode=shutdown
while ! plymouth --ping; do sleep 1; done /bin/plymouth show-splash
But does this make sense?
Should plymouthd really be returning before it is ready to answer requests?
It seems like this behaviour could cause bugs on other non-Ubuntu distributions too (e.g. bug #39774 looks the same)
Regarding this bug: https:/ /bugs.launchpad .net/ubuntu/ +source/ casper/ +bug/966480
The problem is that the Ubuntu plymouthd init script does the equivalent of:
The second command would fail because of the race condition where plymouthd forks and returns, but isn't actually ready to answer connection requests.
The simple fix would be to modify the init script to wait until plymouthd is ready:
while ! plymouth --ping; do sleep 1; done
But does this make sense?
Should plymouthd really be returning before it is ready to answer requests?
It seems like this behaviour could cause bugs on other non-Ubuntu distributions too (e.g. bug #39774 looks the same)