Bug 22180

Summary:	plymouth should coexist better with bootchart
Product:	plymouth	Reporter:	Ray Strode [halfline] <rstrode>
Component:	general	Assignee:	Ray Strode [halfline] <rstrode>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Ray Strode [halfline] 2009-06-09 12:07:41 UTC

Right now plymouth will force the "detailed" splash if init=anything is on the kernel command line.

This is probably the right thing to do for, e.g., init=/bin/sh but the wrong thing to do for, e.g., init=/sbin/bootchartd

We may need to add some sort of plymouth:force-splash or plymouth:splash=default or some such to make the splash show up when bootchartd is running.

Comment 1 Ray Strode [halfline] 2009-06-09 12:07:59 UTC

downstream bug report is here:

https://bugzilla.redhat.com/470136

Comment 2 Frederic Crozat 2009-10-13 09:06:15 UTC

fixed in git :

commit 6e3ae665bc2e1386de7b3396b16a3ffef06c76db
Author: Frederic Crozat <fcrozat@mandriva.com>
Date:   Tue Oct 13 18:01:24 2009 +0200

    [ daemon ] handle plymouth:force-splash on kernel cmdline
    
    When booting with init=..., plymouthd disables itself. It is problematic
    when using bootchartd (bug #22180). plymouth:force-splash allows to
    force plymouthd splash.
    
    Ensure init= value is not used when starting plymouthd for shutdown.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.