Bug 24627 - Passing '+xinerama' on command line to Xorg causes seg fault
Summary: Passing '+xinerama' on command line to Xorg causes seg fault
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Depends on:
Blocks: xserver-1.7.x
  Show dependency treegraph
Reported: 2009-10-19 11:20 UTC by Lee Leahu
Modified: 2010-01-07 16:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

xorg.conf (2.00 KB, application/octet-stream)
2009-10-19 11:20 UTC, Lee Leahu
no flags Details

Description Lee Leahu 2009-10-19 11:20:53 UTC
Created attachment 30564 [details]

GIT Commit - 25344ba7f7845654364d62bf15322b3b79465bd9

/usr/bin/Xorg :0 -ac +xinerama

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7a368d0 (LWP 20287)]
0x080ab4ec in privateExists (privates=0x851b7f8, key=0x0) at privates.c:79
79          return *key && *privates &&
(gdb) bt
#0  0x080ab4ec in privateExists (privates=0x851b7f8, key=0x0) at privates.c:79
#1  0x080ab48c in dixLookupPrivate (privates=0x851b7f8, key=0x0) at privates.c:162
#2  0x080e99c3 in xf86RandR12CreateScreenResources (pScreen=0x851b6a8) at xf86RandR12.c:773
#3  0x080e17c7 in xf86CrtcCreateScreenResources (screen=0x851b6a8) at xf86Crtc.c:727
#4  0x08065a85 in main (argc=4, argv=0xbfd60874, envp=0xbfd60888) at main.c:214
Comment 1 Lee Leahu 2009-10-19 11:22:09 UTC
I forgot to add that this occurs instantaneously.  Xorg does not even fully startup before the crash occurs.
Comment 2 Peter Hutterer 2009-12-08 17:05:35 UTC
Patch for review on the list

Please feel free to add a tested-by or reviewed-by tag if you have done so.
Comment 3 Peter Hutterer 2010-01-07 16:37:11 UTC
commit faca1bc582e374d32ee9d63d10e072fbef4940a3
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Mon Dec 14 11:05:20 2009 +1000

    xfree86: belately init RandR12 if xinerama fails. (#24627)

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.