Bug 362721

Summary: rhgb crashes on first boot, leaving system stuck on stippled X startup screen
Product: [Fedora] Fedora Reporter: Will Woods <wwoods>
Component: rhgbAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: ajax, cra, dcantrell, notting
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-12 10:34:33 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 235704    

Description Will Woods 2007-11-01 18:11:29 EDT
Booting a freshly-installed F8 (rc3) system, X comes up on the stippled screen,
then seems to crash, then starts again, then hangs there. 

Rebooting the system will allow it to start normally on the next boot.

< notting> f13: so, stipple of doom is:
< notting> - rhgb fails
< notting> - firstboot tries to start its own x server
< notting> - something goes wonky where firstboot exits, but x server keeps
running on *vt6*
< notting> - mingetty starts on *vt6*
< notting> - x server is now fubar

I think this also affects the Live images, although slightly differently. rhgb
never manages to start, but since there's no firstboot we end up in GDM. Which
works fine, somehow.
Comment 1 Jeremy Katz 2007-11-01 21:07:56 EDT
"Fixed" with a rhpxl tweak so that we don't hit an exception in the Xserver
startup path and things then go fine.  This is related to the rhgb funnies, though.

Leaving open for that (as they still cause other problems)
Comment 2 Will Woods 2007-11-02 01:09:25 EDT
We're building new (rc4) images that will contain this fix.
Comment 3 Will Woods 2007-11-02 13:08:07 EDT
With the rhpxl tweak and rhgb reverted to rhgb-0.17.7-3.fc8, rhgb is confirmed
to be working OK in RC4 images. Yay! That makes this not-a-blocker.

Leaving the bug open since, as Jeremy said, we're still not sure what was
causing rhgb-8.0.2-1.fc8 to fail in the first place.
Comment 4 Adam Jackson 2008-02-12 10:34:33 EST
rhgb8 never shipped, dutifully ignoring this bug.