Description of problem:
Absolute axes are assigned wrong by the wacom driver. The reason is an extra flag supplied by the driver (OutOfProximity) that's added to the Relative/Absolute setting in the mode field.
Relative and Absolute aren't meant as flags, hence many clients and the server often only have a binary test in the form of
if (mode == Relative) else
if (mode == Absolute) else
With the OutOfProximity flag (0x2) binary OR'd those checks fail, leading to client-implementation dependent interpretation of axis modes.
Version-Release number of selected component (if applicable):
xinput --list --long | less, then look at the axis mode of stylus, eraser (should be absolute by default)
Patch from upstream, simply remove the invalid OutOfProximity flag.
Patch on list archives: http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTimqYpXuEChPzwJ5lDsPZyB4orm24Vmd0ypSQzpz%40mail.gmail.com&forum_name=linuxwacom-devel
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
xorg-x11-drv-wacom-0.10.5-3.el6 is available in brew.
Changing component to xorg-x11-server. The underlying cause turned out to be a problem in the protocol parsing code in the server.
xorg-x11-server-1.7.7-7.el6 is available in brew.
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.