Bug 554480

Summary: Boot Hangs With F12 When Fedora Teardrop/Bubble Is Filled
Product: [Fedora] Fedora Reporter: Jimmy Wilson <jawilson>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: fedora, jawilson, pertusus, rstrode, thomasj, twaugh
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: 2010-01-12 11:15:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jimmy Wilson 2010-01-11 20:07:48 UTC
Description of problem:

Boot hangs on F12 when fedora Teardrop/Bubble is filled with IBM Thinkpad/Lenovo T60.  If hitting Esc or using the nomodeset kernel parameter, boot does not hang.

Version-Release number of selected component (if applicable):

Boot hangs with kernel 2.6.31.5-127 and 2.6.31.9-174.

How reproducible:

Everytime.

Steps to Reproduce:
1. Install F12 from DVD on a IBM Thinkpad/Lenovo T60.
2. Perform "yum update" as root since package manager is broken.
3. Boot that previously worked before yum update, will now hang when the Fedora Teardrop/Bubble is full.

Additional info:

Am Using KDE not Gnome.

Comment 1 Jimmy Wilson 2010-01-11 20:39:44 UTC
I tried to leave the component blank as I could find one that I thought was suitable.  Bugzilla apparently assigned the component, but I don't think what is selected is correct.

Comment 2 Tim Waugh 2010-01-12 10:23:21 UTC
Guessing plymouth, the graphical boot animation program.

Comment 3 Thomas Janssen 2010-01-12 11:15:13 UTC
From what i read is that a duplicate of Bug 551310. I close it as duplicate. Try the solution there. *If* it's not a duplicate, feel free to reopen it. Thanks for reporting the problem.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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