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 1687979 - [X11 Session] Various Wacom Screen Tablets Behave Like the Mode Strip Only has one Mode
Summary: [X11 Session] Various Wacom Screen Tablets Behave Like the Mode Strip Only ha...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-shell
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.2
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 19:54 UTC by Michael Boisvert
Modified: 2022-05-06 00:15 UTC (History)
8 users (show)

Fixed In Version: gnome-shell-3.32.2-14.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:09:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Left Mode Button - libinput record (5.48 KB, text/plain)
2020-01-06 20:20 UTC, Michael Boisvert 		no flags Details
Right Mode Button - libinput record (5.81 KB, text/plain)
2020-01-06 20:20 UTC, Michael Boisvert 		no flags Details
Left Touch Strip - libinput record (8.38 KB, text/plain)
2020-01-06 20:21 UTC, Michael Boisvert 		no flags Details
Right Touch Strip - libinput record (8.21 KB, text/plain)
2020-01-06 20:24 UTC, Michael Boisvert 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-30713 0 None None None 2022-05-06 00:15:17 UTC
Red Hat Product Errata RHSA-2020:1766 0 None None None 2020-04-28 16:09:28 UTC

Description Michael Boisvert 2019-03-12 19:54:47 UTC 
Description of problem: The Cintiq 21UX2 has two rear mounted touch strips with 4 modes, controlled by selection buttons with indicator LEDs. The mode selection LED and OSD shows a mode change, but switching modes doesn't do anything. 

The 24HD has a touch ring with 3 modes, each with its own mode selection button. The same issue is present as well as the modes change in a loop instead of being unique to each button press. 

Steps to Reproduce:
1. Set up a Wacom tablet with mode selection.
2. Map a/b to one of the touchstrip/ring modes and c/d to another mode. 
3. Open gedit and move your finger across the touchstrip/ring, changes modes and try again.

Actual results: The only letters printed will be the first ones mapped, in this case a/b. 

Expected results: Multiple unique modes with different mappings. 

Additional info: So far this issue is present on the two tablets listed above and only on Xorg, not present in Wayland. Also, I cannot check this issue on pen tablets because of bz#1687949.
Comment 1 Carlos Garnacho 2019-12-13 23:59:09 UTC 
I think the problem described with the Cintiq 21UX2 happened to get fixed on 3.32.2-21. It's not that the strips had a single mode, it was that each strip was assigned to the wrong mode switch button (due to libwacom describing them in inverse order). That is now all coherent with that patch.

But this bug also mentions the 24HD multiple mode switch buttons. I have a fix for that.
Comment 2 Carlos Garnacho 2019-12-14 00:23:23 UTC 
Should work with 3.32.2-24
Comment 4 Michael Boisvert 2019-12-17 17:08:00 UTC 
Upon testing with the 24HD and the 21UX2 on mutter-3.32.2-26.el8.x86_64, I do not see these issues as fixed. On the 21UX2, pressing one of the mode switch buttons changes the mode for both touch strips instead of being independent, L and R. It does however have 4 modes for each strip that can be mapped independently. 

On the 24HD, the mode switch LEDs move correctly to each mode but the mapping and OSD never change from mode 1.
Comment 5 Carlos Garnacho 2019-12-23 21:42:23 UTC 
(In reply to Michael Boisvert from comment #4)
> Upon testing with the 24HD and the 21UX2 on mutter-3.32.2-26.el8.x86_64, I
> do not see these issues as fixed. On the 21UX2, pressing one of the mode
> switch buttons changes the mode for both touch strips instead of being
> independent, L and R. It does however have 4 modes for each strip that can
> be mapped independently. 

Hmm... It'd be great if you could attach a couple of evemu/libinput recordings of the pad device, pressing the mode button and going up/down the strip, one for each side.

> 
> On the 24HD, the mode switch LEDs move correctly to each mode but the
> mapping and OSD never change from mode 1.

Gah, silly typo in the patch. I have a fix for that.
Comment 6 Michael Boisvert 2020-01-06 20:19:15 UTC 
(In reply to Carlos Garnacho from comment #5)
> (In reply to Michael Boisvert from comment #4)
> > Upon testing with the 24HD and the 21UX2 on mutter-3.32.2-26.el8.x86_64, I
> > do not see these issues as fixed. On the 21UX2, pressing one of the mode
> > switch buttons changes the mode for both touch strips instead of being
> > independent, L and R. It does however have 4 modes for each strip that can
> > be mapped independently. 
> 
> Hmm... It'd be great if you could attach a couple of evemu/libinput
> recordings of the pad device, pressing the mode button and going up/down the
> strip, one for each side.
> 
> > 
> > On the 24HD, the mode switch LEDs move correctly to each mode but the
> > mapping and OSD never change from mode 1.
> 
> Gah, silly typo in the patch. I have a fix for that.

Okay, I made individual libinput recordings for both touch strips (up then down) and both mode switch buttons (pressed 4x).
Comment 7 Michael Boisvert 2020-01-06 20:20:15 UTC 
Created attachment 1650206 [details]
Left Mode Button - libinput record
Comment 8 Michael Boisvert 2020-01-06 20:20:56 UTC 
Created attachment 1650207 [details]
Right Mode Button - libinput record
Comment 9 Michael Boisvert 2020-01-06 20:21:34 UTC 
Created attachment 1650208 [details]
Left Touch Strip - libinput record
Comment 10 Michael Boisvert 2020-01-06 20:24:52 UTC 
Created attachment 1650210 [details]
Right Touch Strip - libinput record
Comment 15 Michael Boisvert 2020-02-18 19:24:41 UTC 
So yes, the 21UX2 still has errors but so does the 24HD.

With 3.32.2-29 the 24HD doesn't leave mode 1 on either side according to GNOME. However, the LEDs and the button presses on the tablet all line up and function correctly but GNOME never leaves mode 1 and neither does the OSD.
Comment 22 Tomas Popela 2020-03-04 14:14:16 UTC 
Changing the component to a right one (after looking into logs from a conversation with Carlos).
Comment 29 Michael Boisvert 2020-03-05 18:32:13 UTC 
LED mode selection is working properly on gnome-shell-3.32.2-14.el8.
Comment 31 errata-xmlrpc 2020-04-28 16:09:06 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.