Bug 58804 - xinput --map-to-output 10 (keyboard related id) VGA1 (any display) - X segmentation fault
Summary: xinput --map-to-output 10 (keyboard related id) VGA1 (any display) - X segmen...
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xorg (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium critical
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-27 13:43 UTC by Matthew Schultz
Modified: 2017-03-05 05:23 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
xinput_x_crash_backtrace.txt (2.72 KB, text/plain)
2012-12-27 13:43 UTC, Matthew Schultz 		no flags Details
View All

Description Matthew Schultz 2012-12-27 13:43:38 UTC 
Created attachment 72182 [details]
xinput_x_crash_backtrace.txt

If you specify a keyboard device as the device to map the input to with xinput instead of a pointer device, then X will segfault.

where 10 is a keyboard device and VGA1 is a crtc device name from xrandr:

xinput --map-to-output 10 VGA1

I think the expected behavior would be to show an error message saying you can only map pointer devices and not keyboard devices to a crtc.

Tested with xorg 1.13.1 and xinput 1.6.0.
Comment 1 Matthew Schultz 2017-03-05 05:23:53 UTC 
It appears that X no longer segfaults when you specify the wrong device to map to (tested with xorg-server 1.18.4 and xinput 1.6.2):

xinput --map-to-output 12 eDP1
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  57 ()
  Serial number of failed request:  28
  Current serial number in output stream:  29

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.