Bug 51640 - [Intel] use of xorg.conf or xorg.conf.d/ for customizing monitor config causes segfault on X startup
Summary: [Intel] use of xorg.conf or xorg.conf.d/ for customizing monitor config cause...
Status: VERIFIED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-01 18:41 UTC by Felix Miata
Modified: 2012-07-02 10:31 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
(Fedora) Xorg.0.log (8.34 KB, text/plain)
2012-07-01 18:41 UTC, Felix Miata 		no flags Details
View All

Description Felix Miata 2012-07-01 18:41:26 UTC 
Created attachment 63683 [details]
(Fedora) Xorg.0.log

Downstream (server 1.12.2): https://bugzilla.novell.com/show_bug.cgi?id=766059
Today I learned this also happens in Fedora 18, also using server 1.12.2.

To reproduce:
1-create valid xorg.conf file; or 50-monitor.conf file with valid VertRefresh,
PreferredMode and/or DisplaySize lines (along with requisite 50-device.conf &
50-screen.conf files, containing nothing non-default)
2-# startx

Actual behavior:
1-immediate segfault
2-no X
3-too small everything
4-[attached Xorg.0.log]

Expected behavior:
1-X works
2-bigger everything

Notes:
1-Happens on i865, i915 & i945, but not on i810 or nvidia (nv11, g84) or ati (rv200, rv380) chips tested.
2-Both openSUSE 12.2 and Fedora 18 are currently running intel driver 2.19, the former with glamor, the latter apparently without.
Comment 1 Chris Wilson 2012-07-02 01:20:41 UTC 
commit 6138f7434a6fb014299a7e9a8392ef962c8cba30
Author: Cyril Brulebois <kibi@debian.org>
Date:   Tue Jun 12 21:19:14 2012 +0100

    Fix up braindamage in previous commit.
    
    ickle: Fixing up my idiotic change, obviously too much birthday cake.

commit 224d631a232d3536e0f1f2780bfbe1218ee7590f
Author: Cyril Brulebois <kibi@debian.org>
Date:   Tue Jun 12 21:14:53 2012 +0100

    Avoid calling xf86nameCompare() with a NULL string
    
    Device sections without a Driver property would lead to a server
    segfault because of a NULL pointer's being passed as the second
    argument of xf86nameCompare().
    
    Debian bug #677206 <http://bugs.debian.org/677206>
    
    Signed-off-by: Cyril Brulebois <kibi@debian.org>
Comment 2 Felix Miata 2012-07-02 10:31:36 UTC 
Verified fixed for i845, i865, i915 & i945 using xf86-video-intel-2.19.0_20120601_8eed569-18.1.i586 in openSUSE 12.2B2+. Thanks for quick response!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.