Bug 116756

Summary: Fatal server error: no screens found
Product: [Fedora] Fedora Reporter: Walker Aumann <walkera>
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
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: 2006-02-21 19:01:38 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:
Attachments:
Description Flags
/var/log/XFree86.0.log
none
/var/log/messages
none
/etc/X11/XF86Config none

Description Walker Aumann 2004-02-24 22:16:48 UTC 
Description of problem:
gdm can't start - no screens found

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

How reproducible:
Not clear.  gdm won't start with kernel-2.6.3-1.100, but will start
with kernel-2.6.3-1.97.  

Steps to Reproduce:
1. Boot kernel 2.6.3-1.100 with gdm installed and enabled
2.
3.
  
Actual results:
Reports that it can't start X: no screens found.

Expected results:
X (Gnome) starts and allows login.

Additional info:
XFree86.0.log, XF86Config, and /var/log/messages to be attached.
X starts up fine when I boot from kernel-2.6.3-1.97.  So, it's either
a kernel issue or an X issue.
Comment 1 Walker Aumann 2004-02-24 22:17:56 UTC 
Created attachment 98018 [details]
/var/log/XFree86.0.log
Comment 2 Walker Aumann 2004-02-24 22:23:15 UTC 
Created attachment 98019 [details]
/var/log/messages
Comment 3 Walker Aumann 2004-02-24 22:23:39 UTC 
Created attachment 98020 [details]
/etc/X11/XF86Config
Comment 4 Bill Nottingham 2004-02-25 04:32:04 UTC 

*** This bug has been marked as a duplicate of 116724 ***
Comment 5 Mike A. Harris 2004-02-25 11:12:08 UTC 

*** This bug has been marked as a duplicate of 116724 ***
Comment 6 Red Hat Bugzilla 2006-02-21 19:01:38 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.