Bug 18620 - Lack of Screen in ServerLayout makes X segfault
Summary: Lack of Screen in ServerLayout makes X segfault
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-18 20:19 UTC by Dan Williams
Modified: 2009-01-08 20:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Dan Williams 2008-11-18 20:19:19 UTC 
Section "InputDevice"
	Identifier "touchscreen"
	Driver "fujitsu"
	Option "device" "/dev/ttyS0"
	Option "DeviceName" "touchscreen"
	Option "MinX" "82"
	Option "MinY" "146"
	Option "MaxX" "4036"
	Option "MaxY" "3999"
	Option "SendCoreEvents" "On"
EndSection

Section "ServerLayout"
	Identifier "foobar"
	InputDevice "touchscreen" "CorePointer"
EndSection

with xorg-x11-server-Xorg 1.5.3-5.fc10 yields:

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x812bc5b]
1: /usr/bin/X(xf86SigHandler+0x51) [0x80bcc81]
2: [0x130400]
3: /usr/bin/X(InitOutput+0x487) [0x80a3f77]
4: /usr/bin/X(main+0x279) [0x806b519]
5: /lib/libc.so.6(__libc_start_main+0xe5) [0x1a16d5]
6: /usr/bin/X [0x806ab01]


(11:13:04 PM) ajax: oh, except you probably specified a serverlayout that just mentions input devices, and no video devices
(11:13:11 PM) dcbw: ajax: ding ding ding
(11:13:12 PM) ajax: and then the code probably doesn't handle that
(11:13:24 PM) ajax: but the offending line is:
(11:13:28 PM) ajax:     GDevPtr configured_device = xf86ConfigLayout.screens->screen->device;
Comment 1 Peter Hutterer 2008-11-19 16:36:43 UTC 
Dupe of 16301?

Looks like fe5cf7cb00fd926cefff933adbdbceea7353f4c2 needs to get
cherry-picked, can you test this please?
Comment 2 Peter Hutterer 2009-01-08 20:45:37 UTC 
No reply for over 30 days. Closing.

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.