Bug 618422 - Wrong handling of devices with more than 2 valuators
Summary: Wrong handling of devices with more than 2 valuators
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-server
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Peter Hutterer
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Keywords: Regression
Depends On:
Blocks: 607150
TreeView+ depends on / blocked
 
Reported: 2010-07-26 21:54 UTC by Peter Hutterer
Modified: 2010-11-10 21:59 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-11-10 21:59:09 UTC


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.