Bug 1370321

Summary: Wacom 22HD Touchscreen Incorrectly Mapping to both Monitors in Dual Head Configuration
Product: Red Hat Enterprise Linux 6 Reporter: Peter Hutterer <peter.hutterer>
Component: libwacomAssignee: Peter Hutterer <peter.hutterer>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7CC: desktop-qa-list, jkoten, mboisver, peter.hutterer, skomra, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1216221 Environment:
Last Closed: 2017-12-06 12:14:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1392665    
Bug Blocks: 1216221, 1360926    

Comment 11 Peter Hutterer 2016-11-08 02:17:18 UTC
Putting this fix into libwacom is not as reliable as would be expected from an enterprise distribution. While the mapping can be made to work it is a hidden side-effect of the GNOME implementation for tablets. When the mapping fails, it may overwrite any attempts by the users to change the mapping later. And any fix in libwacom would apply to the specific device only (Cintiq 22HD in this case) when the mapping issue is a larger problem seen by touchscreens on RHEL6.

Suggested workaround to be run by a user to ensure the tablet is mapped to a monitor when required:

First, run xinput list to identify the device to be mapped. The output will look approximately like this:
$> xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® 2.4GHz Transceiver v9.0	id=10	[slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® 2.4GHz Transceiver v9.0	id=11	[slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 22HDT Pen stylus           	id=13	[slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 22HDT Pen eraser           	id=14	[slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 22HDT Pen pad              	id=15	[slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 22HDT Finger touch         	id=16	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Microsoft Microsoft® 2.4GHz Transceiver v9.0	id=9	[slave  keyboard (3)]
    ↳ Yubico Yubico Yubikey II                	id=12	[slave  keyboard (3)]

The device to map is the "Wacom Cintiq 22HDT Finger touch" device. Now run xrandr to identify the output name:
$> xrandr
Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
DP2 connected primary 1920x1200+1920+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   1920x1080     59.99  
   1600x1200     60.00  
   1680x1050     59.95  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.00  
   800x600       60.32  
   640x480       60.00  
   720x400       70.08  
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VGA1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   1920x1080     59.99  
   1600x1200     60.00  
   1680x1050     59.95  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.00  
   800x600       60.32  
   640x480       60.00  
   720x400       70.08  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

To map the Cintiq to output DP2, the following command should be run:
   xinput map-to-output "Wacom Cintiq 22HDT Finger touch" "DP2"

This command can be adjusted for other tablets that require similar mapping. As the name and output stay the same for a device, this command can be re-used after reboots.

Until there is a desktop-integrated solution (see Bug 1392665) users are requested to run the above command to get the screen mapping as required.

Comment 15 Jan Kurik 2017-12-06 12:14:08 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/