On my system /usr is a seperate read-only-mounted partition. This means that Plymouth fails horribly since it requires stuff from /usr to initialize properly, such as libpng and during earily bootup that dir is not available yet.
Generally libraries/binaries installed in / should not depend on things from /usr. But more importantly, stuff that is needed for early boot shouldn't depend on anything from /usr.
Plymouth spams the console with a lot of errors when booting up with a seperate /usr partition. It doesn't bring anything useful on the screen but steals the cursor and puts the terminal in some strange mode so that you cannot even use the console anymore to see what is going on.
libpng is put in the initrd, that's probably not the issue.
it's probably /usr/bin/plymouth using /usr/lib/libply
Why do you use a separate /usr partition by the way?
oh libply.so links against libpng.so event though /usr/bin/plymouth doesn't need libpng...that's probably fixable
*** Bug 464220 has been marked as a duplicate of this bug. ***
Since this makes my system unbootable and apparently we *do* allow setups with seperate /usr I am take the freedom to make this a F10Blocker.
Please, please, please, with cream on top: let me be able boot my system properly again!
yea it should be on the blocker list.
I've moved a bunch of stuff around on the filesystem, so /usr shouldn't be needed anymore.
Hopefully I didn't break anything, but it was a lot of little changes, so I wouldn't be surprised if I did.
I'm going to close this, but please reopen if you still see an issue.
To test, install the latest plymouth then rebuild your initrd with:
/sbin/mkinitrd -f /boot/initrd-kernel-version-here.img kernel-version-here
*** Bug 465706 has been marked as a duplicate of this bug. ***
Seems to work now.