Bug 464216

Summary:	Plymouth shouldn't depend on things from /usr
Product:	[Fedora] Fedora	Reporter:	Lennart Poettering <lpoetter>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	krh, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-06 19:39:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	438943

Description Lennart Poettering 2008-09-26 18:45:19 UTC

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.

Comment 1 Ray Strode [halfline] 2008-09-26 21:13:13 UTC

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?

Comment 2 Ray Strode [halfline] 2008-09-26 21:14:50 UTC

oh libply.so links against libpng.so event though /usr/bin/plymouth doesn't need libpng...that's probably fixable

Comment 3 Ray Strode [halfline] 2008-09-29 21:40:00 UTC

*** Bug 464220 has been marked as a duplicate of this bug. ***

Comment 4 Lennart Poettering 2008-10-05 20:25:41 UTC

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!

Comment 5 Lennart Poettering 2008-10-05 20:28:16 UTC

s/take/taking/

Comment 6 Ray Strode [halfline] 2008-10-05 21:44:56 UTC

yea it should be on the blocker list.

Comment 7 Ray Strode [halfline] 2008-10-06 19:39:14 UTC

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

Comment 8 Ray Strode [halfline] 2008-10-06 19:43:49 UTC

*** Bug 465706 has been marked as a duplicate of this bug. ***

Comment 9 Lennart Poettering 2008-10-10 20:35:22 UTC

Seems to work now.