Bug 618422

Summary: Wrong handling of devices with more than 2 valuators
Product: Red Hat Enterprise Linux 6 Reporter: Peter Hutterer <peter.hutterer>
Component: xorg-x11-serverAssignee: Peter Hutterer <peter.hutterer>
Status: CLOSED CURRENTRELEASE QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: mgordon, syeghiay
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: xorg-x11-server-1.7.7-22.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:59:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 607150    

Description Peter Hutterer 2010-07-26 21:54:51 UTC
Description of problem:
Fix to Bug 607150 introduces a regression in the handling of devices with more than two axes. A full description of (and proposed fix for) the issue is available here:
http://lists.freedesktop.org/archives/xorg-devel/2010-July/011355.html

Version-Release number of selected component (if applicable):
xorg-x11-server-1.7.7-17.el6

How reproducible:
Reproducible by using e.g. a wacom tablet and generating button releases on the
tablet - the log will fill up with "too many valuators" error messages.

Comment 3 Peter Hutterer 2010-07-28 05:54:46 UTC
MODIFIED

xorg-x11-server-1.7.7-22.el6 is available in brew.

Comment 5 Mark Gordon 2010-08-16 18:16:30 UTC
Verified with a Lenovo T60 and a Wacom PTK-440.  Installed an old compose that had the broken version to confirm that I could reproduce the bug, then installed a recent compose with the fix to confirm that I could no longer reproduce the bug.  Confirmed that the bug is fixed in both i686 and x86_64.

-> VERIFIED

Comment 6 releng-rhel@redhat.com 2010-11-10 21:59:09 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.