After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698284 - Missing feature causes weird behavior when using touchscreen when two (or more) monitors are present
Missing feature causes weird behavior when using touchscreen when two (or mor...
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: xrandr
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
touch
Depends on:
Blocks:
 
 
Reported: 2013-04-18 10:37 UTC by Elad Alfassa
Modified: 2014-05-21 09:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Elad Alfassa 2013-04-18 10:37:43 UTC
<elad> hadess: when I touch the screen the cursor disappears, but stuff happens on the external screen and nothing happens on the regular screen
<elad> somehow it maps the touches wrong? I don't know
<hadess> fwiw, it's not a bug, more of a missing feature
<hadess> there's no way to know that the touchscreen is linked to this xrandr output
Comment 1 Peter Hutterer 2013-04-19 03:01:50 UTC
check the "Coordinate Transformation Matrix" property and calculate based on that. we don't map touchscreens to an output, we map it to a portion of the desktop. I admit that this isn't ideal and for complex setups won't work but for the 90% case deconstructing the matrix can identify the output.

or am I misreading this and you're referring that we don't know how the physical tablet is set up? tbh, I don't know how to fix this other than a database in the style of libwacom
Comment 2 Elad Alfassa 2014-02-22 00:44:18 UTC
Only now saw this comment. Probably got lost in my bugmail.

It's a multitouch laptop screen. To the laptop, I attached a regular, non-touch screen. So my setup is [small laptop touchscreen][big external screen].

When I touch something on the touchscreen, things happen on the external screen, and not the laptop screen: the system behaves as if I made a mouse click somewhere on the external screen, which is obviously a wrong behavior.

This setup is not really that complex, and I'd expect it to work.
Comment 3 Carlos Garnacho 2014-05-20 13:45:11 UTC
Elad, Is this fixed for you in gnome-settings-daemon >= 3.12? Builtin touchscreen mapping should behave a lot better there. 

If this is no longer an issue, feel free to close the bug. Otherwise, it'd be appreciated that you attached the debug logs (obtained through gnome-settings-daemon -r --debug) of a recent g-s-d version.
Comment 4 Elad Alfassa 2014-05-21 09:58:38 UTC
I can confirm this is fixed in >= 3.12

Thanks!