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 1635392 - Mutter Causing Odd/Bad Button Mapping Behavior on Wacom Tablets
Summary: Mutter Causing Odd/Bad Button Mapping Behavior on Wacom Tablets
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mutter
Version: 7.6
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Carlos Garnacho
QA Contact: Desktop QE
Marie Hornickova
URL:
Whiteboard:
Depends On:
Blocks: 1637822
TreeView+ depends on / blocked
 
Reported: 2018-10-02 19:46 UTC by Michael Boisvert
Modified: 2019-08-06 12:38 UTC (History)
11 users (show)

Fixed In Version: 7.0
Doc Type: If docs needed, set a value
Doc Text:
Button mapping does not work on Wacom tablets After upgrading the _mutter_ package to version mutter-3.28.3-2.el7 or newer, button mapping and the scroll wheel function mapping does not work on Wacom tablets. Consequently, the mapped function does not occur after pressing the button. To work around this problem ...
Clone Of:
: 1637822 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:37:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2044 0 None None None 2019-08-06 12:38:19 UTC

Description Michael Boisvert 2018-10-02 19:46:51 UTC 
Description of problem: Upgrade to mutter-3.28.3-2.el7 causes two distinct problems with pad buttons on Wacom tablets. Firstly, after mapping a button to something like "alt+f2" you now have to click and hold in order for the button to function. Second, mapping the scroll wheel function doesn't seem to work unless its a very basic key like UP or DOWN. I can reproduce old and new functionality seamlessly by downgrading and upgrading just mutter package.  

Version-Release number of selected component: mutter-3.28.3-2.el7 (or newer)

Steps to Reproduce:
1. Install 7.6 with mutter-3.28.3-2.el7 or newer.
2. Map any button on a Wacom tablet to something obvious like "alt+f2."
3. Quickly press mapped button. 

Actual results: Nothing happens (unless held for 1 second).

Expected results: Mapped function occurs immediately. 

Additional info: This seems fairly serious and I would propose be fixed in a 7.6 z-stream scenario.
Comment 12 Marie Hornickova 2018-10-10 16:28:46 UTC 
Hi Michael,

This bug is on the list of candidates to be described in RHEL 7.6 Release Notes.

I tried to create the initial draft description according to the information that you've provided in the very first comment.

Please, could you review the doc text whether it is accurate content-wise and add the work around?

Another question is that whether this should be described as a known issue or whether it's expected that it'll be fixed with 7.6 GA release and that case I should wait with the description until it's fixed?

Thanks a lot for your help!

Marie
Comment 13 Michael Boisvert 2018-10-23 12:17:12 UTC 
(In reply to Marie Dolezelova from comment #12)
> Hi Michael,
> 
> This bug is on the list of candidates to be described in RHEL 7.6 Release
> Notes.
> 
> I tried to create the initial draft description according to the information
> that you've provided in the very first comment.
> 
> Please, could you review the doc text whether it is accurate content-wise
> and add the work around?
> 
> Another question is that whether this should be described as a known issue
> or whether it's expected that it'll be fixed with 7.6 GA release and that
> case I should wait with the description until it's fixed?
> 
> Thanks a lot for your help!
> 
> Marie

Marie, there is no real workaround apart from clicking and holding the button you desire. It is fixed as a 7.6.z 0day.
Comment 14 Marie Hornickova 2018-10-25 10:30:53 UTC 
(In reply to Michael Boisvert from comment #13)
> (In reply to Marie Dolezelova from comment #12)
> > Hi Michael,
> > 
> > This bug is on the list of candidates to be described in RHEL 7.6 Release
> > Notes.
> > 
> > I tried to create the initial draft description according to the information
> > that you've provided in the very first comment.
> > 
> > Please, could you review the doc text whether it is accurate content-wise
> > and add the work around?
> > 
> > Another question is that whether this should be described as a known issue
> > or whether it's expected that it'll be fixed with 7.6 GA release and that
> > case I should wait with the description until it's fixed?
> > 
> > Thanks a lot for your help!
> > 
> > Marie
> 
> Marie, there is no real workaround apart from clicking and holding the
> button you desire. It is fixed as a 7.6.z 0day.


Hi Michael,

Thanks a lot for this info. 
If it is fixed as a 7.6.z 0day, does it mean that we do not need the description of this known issue for Release Notes?

Thank you!
Marie
Comment 15 Marie Hornickova 2018-10-25 12:32:11 UTC 
OK, so I got the info from my colleague that what is fixed as 7.6 0 day does not come into RN. So I'm removing this from Release Notes repo.
Comment 16 Michael Boisvert 2018-10-25 13:48:01 UTC 
(In reply to Marie Dolezelova from comment #15)
> OK, so I got the info from my colleague that what is fixed as 7.6 0 day does
> not come into RN. So I'm removing this from Release Notes repo.

That is correct.
Comment 18 Michael Boisvert 2019-05-07 18:47:53 UTC 
Verified on mutter-3.28.3-10.el7.
Comment 20 errata-xmlrpc 2019-08-06 12:37:45 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/RHBA-2019:2044
Note You need to log in before you can comment on or make changes to this bug.