RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1777556 - [Wayland] Various Wacom Screen Tablet Functions Displayed on Incorrect Screen
Summary: [Wayland] Various Wacom Screen Tablet Functions Displayed on Incorrect Screen
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mutter
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.3
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1739559 1980804
TreeView+ depends on / blocked
 
Reported: 2019-11-27 19:54 UTC by Michael Boisvert
Modified: 2021-07-09 15:12 UTC (History)
4 users (show)

Fixed In Version: mutter-3.32.2-25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1980804 (view as bug list)
Environment:
Last Closed: 2020-04-28 16:10:14 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
gbus call 21UX2 (5.01 KB, text/plain)
2020-01-16 18:33 UTC, Michael Boisvert 		no flags Details
libinput list-devices (8.13 KB, text/plain)
2020-01-16 18:37 UTC, Michael Boisvert 		no flags Details
xinputlist (1.51 KB, text/plain)
2020-01-16 18:43 UTC, Michael Boisvert 		no flags Details
xinputlistprops (1.37 KB, text/plain)
2020-01-16 18:44 UTC, Michael Boisvert 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1766 0 None None None 2020-04-28 16:10:37 UTC

Description Michael Boisvert 2019-11-27 19:54:14 UTC 
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.
Comment 1 Carlos Garnacho 2019-12-14 00:55:22 UTC 
Fixed in 3.32.2-25
Comment 3 Michael Boisvert 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?
Comment 4 Carlos Garnacho 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
Comment 5 Michael Boisvert 2020-01-16 18:33:55 UTC 
Created attachment 1652864 [details]
gbus call 21UX2
Comment 6 Michael Boisvert 2020-01-16 18:37:45 UTC 
Created attachment 1652877 [details]
libinput list-devices
Comment 7 Michael Boisvert 2020-01-16 18:43:52 UTC 
Created attachment 1652879 [details]
xinputlist
Comment 8 Michael Boisvert 2020-01-16 18:44:18 UTC 
Created attachment 1652880 [details]
xinputlistprops
Comment 9 Michael Boisvert 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.
Comment 14 Michael Boisvert 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?
Comment 15 Carlos Garnacho 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.
Comment 16 Michael Boisvert 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
Comment 17 Michael Boisvert 2020-02-25 14:58:49 UTC 
Verifying this for now, see above comment for remaining issues.
Comment 18 Michael Boisvert 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
Comment 20 errata-xmlrpc 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
Note You need to log in before you can comment on or make changes to this bug.