Red Hat Bugzilla – Bug 1029612
22HD Touchscreen Incorrectly Controls Both Monitors
Last modified: 2017-07-03 11:06:21 EDT
Description of problem:
When using the Cintiq 22HD touch with a dual screen setup, the touchscreen is incorrectly mapped to the entire span of both monitors. It should just be limited to its own display. The stylus is correctly mapped.
Steps to Reproduce:
1. Install RHEL7.0
2. Create a dual monitor setup (laptop + 22HD)
3. Try using the touchscreen.
Actual results: The touchscreen incorrectly controls the entire span of both monitors.
Expected results: The touchscreen controls its own display regardless of a multi monitor setup.
verified, this will affect all wacom devices that have the touchscreen on a separate device. Waiting for feedback from the GNOME guys on how this will be addressed, the libwacom change is only one part of the solution and a more generic solution may be sought.
*** Bug 1051414 has been marked as a duplicate of this bug. ***
reassigning. this affects all touchscreens including non-wacom ones and should be handled by the desktop environment.
Carlos is working on a fix for this - currently being tested.
The corresponding (growingly generic) upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=709600
I've attached 3 patches there that fix the issue. As for RHEL suitability, the changes to the wacom module are maybe too intrusive, as this module goes already to great lengths to map pens/erasers correctly, the change to GsdDeviceMapper is perhaps more dubious as brings less benefits.
OTOH touchscreen management in the Xrandr module is certainly broken on quite a few situations, so these changes can only improve things, and these are the changes this bug is interested in.
Btw, I forgot to mention that I tested the package (since first build ...) and it resolves the problem. My wacom is now properly tied to the specified monitor only.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.