Bug 875474

Summary: Regression: no graphical display after plymouth update
Product: [Fedora] Fedora Reporter: Mattia Verga <mattia.verga>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 18CC: awilliam, fedora, kparal, robatino, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-15 15:13:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 752660    

Description Mattia Verga 2012-11-11 14:08:31 UTC
After updating to Plymouth* 0.8.8.3 boot process halts on
[FAILED] Failed to start Wait for Plymouth Boot screen to quit.

see 'system status plymouth-quit-wait.servioce' for details

[OK] Reached target multi user.

[OK] Reached target graphical interface

Downgrading to plymouth* 0.8.7.1 solves the problem.

Comment 1 Mattia Verga 2012-11-14 16:57:37 UTC
See this discussion on Fedoraforum:
http://forums.fedoraforum.org/showthread.php?t=285731

I don't think plymouth 0.8.8.3 should land in Beta...

Comment 2 Ray Strode [halfline] 2012-11-14 17:16:34 UTC
does running "dracut -f" fix the problem for you?

Comment 3 Ray Strode [halfline] 2012-11-14 17:17:02 UTC
(after 0.8.3-3 is reinstalled of course)

Comment 4 Kamil Páral 2012-11-14 18:04:24 UTC
Discussed at 2012-11-14 blocker bug meeting. We need more information on whether or not rebuilding the initramfs fixes the issue described here before deciding on blocker status. Please try "dracut -f" fix and report back, thank you.

Comment 5 Mattia Verga 2012-11-15 12:14:51 UTC
Yes, after updating to 0.8.8-3 and run 'dracut -f' problem is fixed.

Comment 6 Ray Strode [halfline] 2012-11-15 15:13:05 UTC
great, closing then.

Comment 7 Adam Williamson 2012-11-16 02:25:49 UTC
this is clearly a dupe of the well-known issue in 0.8.8-1.

*** This bug has been marked as a duplicate of bug 870695 ***