Bug 1635392

Summary:	Mutter Causing Odd/Bad Button Mapping Behavior on Wacom Tablets
Product:	Red Hat Enterprise Linux 7	Reporter:	Michael Boisvert <mboisver>
Component:	mutter	Assignee:	Carlos Garnacho <cgarnach>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	urgent	Docs Contact:	Marie Hornickova <mdolezel>
Priority:	high
Version:	7.6	CC:	bgollahe, btissoir, cgarnach, mboisver, mclasen, nobody+bgollahe, peter.hutterer, rstrode, salmy, toneata, tpelka
Target Milestone:	rc	Keywords:	Regression, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
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 ...	Story Points:	---
Clone Of:
Clones:	1637822 (view as bug list)		Environment:
Last Closed:	2019-08-06 12:37:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1637822

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