Bug 1496659

Summary: Fix device flags for the 13HD, MobileStudio and the 2nd gen Intuos Pro
Product: Red Hat Enterprise Linux 7 Reporter: Peter Hutterer <peter.hutterer>
Component: xorg-x11-drv-wacomAssignee: Peter Hutterer <peter.hutterer>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: mboisver, peter.hutterer, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: xorg-x11-drv-wacom-0.34.2-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 11:52:21 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:

Description Peter Hutterer 2017-09-28 04:40:12 UTC 
Description of problem:
The driver-internal flags are wrong for a set of devices, including the one in $SUBJECT. This causes the driver to initialize the wrong features (e.g. missing touch rings or rotation)

Version-Release number of selected component (if applicable):
xorg-x11-drv-wacom-0.34.2

How reproducible:
Plug in a Intuos Pro 2 M or L and run xinput list "the pad device name". Notice the ring is initialized to 0/1, not 0/71 as it should be.

Additional info:
The Pro 2 M/L may not yet be supported in the kernel, that'd be a separate issue though.
Comment 2 Peter Hutterer 2017-10-05 04:10:11 UTC 
xorg-x11-drv-wacom-0.34.2-3.el7 is available in brew
Comment 8 Michael Boisvert 2018-02-08 18:41:16 UTC 
After speaking with Peter, we can verify this.
Comment 12 errata-xmlrpc 2018-04-10 11:52:21 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-2018:0736