Bug 621990

Summary: Cannot start X with large external monitor attached
Product: [Fedora] Fedora Reporter: ell1e <el>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: ajax, xgl-maint
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-08-25 19:58:33 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
The output of X to the TTY when attempting to start it up (through startx)
none
Xorg.0.log of the incident none

Description ell1e 2010-08-06 17:27:49 UTC 
Created attachment 437217 [details]
The output of X to the TTY when attempting to start it up (through startx)

Description of problem:
X fails to startup with a large external monitor (1680x1050) attached. Removing the monitor, starting X and attaching/configuring the monitor afterwards works flawlessly. The machine is an Asus Eee laptop (intel renderer details see under Additional info) with a native screen of 1024x600.

Version-Release number of selected component (if applicable):
Intel 2.12.0 installed from http://www.scrye.com/~kevin/fedora/xorg-intel/  

How reproducible:
100% (tried multiple times)

Steps to Reproduce:
1. Attach large monitor
2. Use "startx"
  
Actual results:
X fails to start with an error message (see attached X output and Xorg.0.log)

Expected results:
X starts

Additional info:
bash-4.1$ glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL renderer string: Mesa DRI Intel(R) 945GME GEM 20100328 2010Q1 
OpenGL version string: 1.4 Mesa 7.8.1
bash-4.1$
Comment 1 ell1e 2010-08-06 17:32:41 UTC 
Created attachment 437220 [details]
Xorg.0.log of the incident
Comment 2 ell1e 2010-08-14 18:18:29 UTC 
I forwarded the bug to bugs.freedesktop.org:

https://bugs.freedesktop.org/show_bug.cgi?id=29577