Cloned because the same thing is occurring in RHEL 9.0. For the most part it is just calibration that is incorrectly displayed.

+++ This bug was initially created as a clone of Bug #1777556 +++

Description of problem: On most Wacom screen tablets, calibrate and map button overlays are displayed on the native display instead of the Wacom tablet itself.

Setup:
Lenovo X230T with built in Wacom touch screen tablet
Wacom Cintiq 21UX, 22HDT, 22HD, 27QHD, 24HD (assuming others as well)
Screens set up as joined displays L+R.

Steps to Reproduce:
1. With the above setup, open the Wacom settings and select Calibrate for the connected tablet (21UX, 22HDT, 22HD, 27QHD, 24HD)

Actual results: The interactive calibration prompt is displayed on the laptop native display instead of the screen tablet plugged in. 

Expected results: Calibration and button mapping should be unique to each device.

--- Additional comment from Carlos Garnacho on 2019-12-14 00:55:22 UTC ---

Fixed in 3.32.2-25

--- Additional comment from errata-xmlrpc on 2019-12-14 08:12:53 UTC ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2019:47130-02
https://errata.devel.redhat.com/advisory/47130

--- Additional comment from Michael Boisvert on 2019-12-17 16:55:56 UTC ---

With a fresh 8.2 install with mutter-3.32.2-26.el8.x86_64, I do not see this as fixed. I tested calibration and button mapping with the 22HD and 22HDT and both functions are displayed on the laptop's native screen instead of the tablet. How can I help, what logs are needed?

--- Additional comment from Carlos Garnacho on 2019-12-23 21:42:46 UTC ---

If the mapping fails with this patch in place, there's 2 reasons I can think about:

- The tablet output is somehow "hard coded" in gsettings
- The display/tablet mapping is broken for the 22HD

You say this is a fresh install, so shouldn't be the first (double check the "output" setting in "/org/gnome/desktop/peripherals/tablets/056a:00fa" and "/org/gnome/desktop/peripherals/tablets/056a:005b" though)

Assuming it's the latter, I'd appreciate the output of:
- "gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Mutter/DisplayConfig --method org.gnome.Mutter.DisplayConfig.GetResources" with the output plugged in.
- "sudo libinput list-devices"
- "xinput list <deviceid>" and "xinput list-props <deviceid>" for the stylus device on xorg

--- Additional comment from Michael Boisvert on 2020-01-16 18:33:55 UTC ---



--- Additional comment from Michael Boisvert on 2020-01-16 18:37:45 UTC ---



--- Additional comment from Michael Boisvert on 2020-01-16 18:43:52 UTC ---



--- Additional comment from Michael Boisvert on 2020-01-16 18:44:18 UTC ---



--- Additional comment from Michael Boisvert on 2020-01-16 18:45:28 UTC ---

Should have everything you asked for. Seems like the map buttons OSD is appearing on the wrong display in Xorg too.

--- Additional comment from Tomas Pelka on 2020-01-29 14:41:29 UTC ---

Hey Carlos what is your plan with this bz.

Thanks
-Tom

--- Additional comment from Carlos Garnacho on 2020-02-13 22:56:46 UTC ---

The changes in 3.32.2-29 should fix the location for the pad button configuration OSD

However it won't help for the calibration UI... I realized that I painted myself to a corner here, and I am quite afraid it is not trivial to fix for 8.2.0.

IIUC if the mapping fails, it should still appear in the current monitor, so there is a workaround that can be documented.

--- Additional comment from errata-xmlrpc on 2020-02-14 07:23:47 UTC ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2019:47130-02
https://errata.devel.redhat.com/advisory/47130

--- Additional comment from Tomas Pelka on 2020-02-14 08:22:35 UTC ---

Hi Mike can you please verify with latest mutter (-29 I think).

Thanks
-Tom

--- Additional comment from Michael Boisvert on 2020-02-18 19:44:05 UTC ---

Results as follows:

22HDT: Calibrate and Map Buttons: Wrong display.
21UX2: Calibrate wrong, Map Buttons correct.
22HD: Calibrate wrong, Map Buttons correct.
21UX: Calibrate wrong, Map Buttons correct.
27QHD: Calibrate wrong, can't map buttons.

So in general the button mapping is now displayed correctly but calibration is not. Should we verify this and file new bug(s) for the remaining issues?

--- Additional comment from Carlos Garnacho on 2020-02-20 15:25:43 UTC ---

IMHO it's the best way forward. It sounds the remaining cases like the 22HDT are distinct ones. For the 27QHD it'd make sense to handle in a separate bug if the EKR cannot be mapped.

--- Additional comment from Michael Boisvert on 2020-02-25 14:56:42 UTC ---

(In reply to Carlos Garnacho from comment #15)
> IMHO it's the best way forward. It sounds the remaining cases like the 22HDT
> are distinct ones. For the 27QHD it'd make sense to handle in a separate bug
> if the EKR cannot be mapped.

RHEL8 EKR bug: https://bugzilla.redhat.com/show_bug.cgi?id=1638517
RHEL8 22HDT bug: https://bugzilla.redhat.com/show_bug.cgi?id=1807058

--- Additional comment from Michael Boisvert on 2020-02-25 14:58:49 UTC ---

Verifying this for now, see above comment for remaining issues.

--- Additional comment from Michael Boisvert on 2020-02-25 19:30:41 UTC ---

(In reply to Michael Boisvert from comment #16)
> (In reply to Carlos Garnacho from comment #15)
> > IMHO it's the best way forward. It sounds the remaining cases like the 22HDT
> > are distinct ones. For the 27QHD it'd make sense to handle in a separate bug
> > if the EKR cannot be mapped.
>
 
RHEL8 EKR bug: https://bugzilla.redhat.com/show_bug.cgi?id=1638517
RHEL8 22HDT bug: https://bugzilla.redhat.com/show_bug.cgi?id=1807058
RHEL8 Remaining Calibration issues bug: https://bugzilla.redhat.com/show_bug.cgi?id=1807200

--- Additional comment from errata-xmlrpc on 2020-04-28 00:03:31 UTC ---

Bug report changed to RELEASE_PENDING status by Errata System.
Advisory RHSA-2019:47130-06 has been changed to PUSH_READY status.
https://errata.devel.redhat.com/advisory/47130

--- Additional comment from errata-xmlrpc on 2020-04-28 16:10:14 UTC ---

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.

https://access.redhat.com/errata/RHSA-2020:1766