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 783752 - Wacom tablet cannot Map to Monitor properly with dual/multiple monitors/screens
Wacom tablet cannot Map to Monitor properly with dual/multiple monitors/screens
Status: RESOLVED DUPLICATE of bug 782032
Product: gnome-control-center
Classification: Core
Component: Wacom
3.24.x
Other Linux
: Normal major
: ---
Assigned To: Carlos Garnacho
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-06-13 14:27 UTC by Tyson Tan
Modified: 2017-06-30 07:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tyson Tan 2017-06-13 14:27:42 UTC
In Ubuntu Gnome 17.04, Wacom tablet cannot be properly mapped using the "Map to Monitor" dialogue provided by gnome-control-center's Wacom panel. It's always mapped to the first monitor, and the ratio is incorrect. Both Wayland and Xorg sessions are affected. It has never happened with Gnome 3.20, 3.22.

From my experience with a similar problem in the past, I suspect the problem has something to do with:
1) gnome-control-center
2) gnome-settings-daemon (g-s-d)
3) mutter

My hardware setup:
1) Cintiq 13HD (1920x1080, HDMI through adaptor)
2) NEC PA242W (1920x1200, Displayport)
3) Intuos 4M
4) AMD FirePro W5100 (4 DisplayPorts)

Another hardware setup with different GPU and display but has the same result.
1) Dell 2209WA (1680x1050, DVI)
2) AMD Radeon R7 250E (DVI, DisplayPort)

Detail:

1) When "Map to single monitor" is OFF, Intuos 4M's cursor moves between both monitors.
2) When "Map to single monitor" is ON, Intuos 4M's cursor moves ONLY on the first monitor(that connects to the GPU output of the highest priority). 
3) For example, my GPU has 4 DisplayPort outputs, when I turn on "Map to single monitor", my Intuos 4M is always mapped to whatever on DisplayPort-1 regardless of what I choose in Display Mapping dialogue's output droplist.
4) When a secondary monitor is present, cursor on Cintiq is not aligned with the pentip. Both of the single monitors are 16:10, Cintiq 13HD is 16:9. I suspect this to be relevant with this bug.

This bug has also been reported to Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1697701
Comment 1 Tyson Tan 2017-06-13 14:28:59 UTC
It also happens on Manjaro 17.0.1 and some other distros with Gnome 3.24.x.
Comment 2 Jason Gerecke 2017-06-15 17:40:05 UTC
Does this differ from bug 782032, and if so -- how?
Comment 3 Tyson Tan 2017-06-16 08:14:04 UTC
(In reply to Jason Gerecke from comment #2)
> Does this differ from bug 782032, and if so -- how?

1) No, I think they are the same. 

2) Bug 782032 did not receive any attention from Gnome, 1 month after it was first reported. I was worried that the Gnome developers missed it.

3) This bug affects artists in a major way, breaking their working environment completely. It is too important to be left unnoticed. Dual display is such a common setup for artists and I hope Gnome developers can do some more test for it next time.

4) Bug 782032 did not show up when I was searching with Google, I felt I have to report it again with a different style of title, keyword and description, hopefully when the next affected Linux artist is trying to search the web, they at least know they are not crazy/alone!

5) Improved Wacom support was in Gnome 3.24's release notes. And with it, I can't use my Wacom anymore! It burned so bad when I upgraded to Ubuntu Gnome 17.04 with all the hopes and dreams! For now I seek refuge under Fedora 25 (Gnome 3.22) but for how long? The time is running out -- Fedora 26 is on the horizon with Gnome 3.24! Ah! The Apocalypse! I start to panic and have dreams about being forced to use OpenSUSE 42.2 with Gnome 3.20. When that's also nucleared we are back to the stone age of Debian 8.8 with Gnome 3.14! *shiver*

* Don't take (5) seriously. XD
Comment 4 Jason Gerecke 2017-06-16 15:22:18 UTC
(In reply to Tyson Tan from comment #3)
> 
> * Don't take (5) seriously. XD

Totally get where you're coming from ;) Wayland tablet support under 3.24 is definitely not where I would have expected it to be given the announcement. Hopefully the most egregious bugs will be dealt with before 3.26.
Comment 5 Carlos Garnacho 2017-06-29 23:10:56 UTC
(In reply to Jason Gerecke from comment #4)
> (In reply to Tyson Tan from comment #3)
> > 
> > * Don't take (5) seriously. XD
> 
> Totally get where you're coming from ;) Wayland tablet support under 3.24 is
> definitely not where I would have expected it to be given the announcement.
> Hopefully the most egregious bugs will be dealt with before 3.26.

FWIW I'm backporting those to 3.24.

*** This bug has been marked as a duplicate of bug 782032 ***
Comment 6 Tyson Tan 2017-06-30 07:47:01 UTC
Thank you, Carlos.