Your message dated Sun, 22 Feb 2009 21:42:34 +1030
with message-id <[email protected]>
and subject line Re: Bug#516537: wacom: X does not automatically translate
tablet coords to screen coords in core events
has caused the Debian Bug report #516537,
regarding wacom: X does not automatically translate tablet coords to screen
coords in core events
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
516537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516537
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xserver-xorg-input-wacom
Version: 0.8.1.6-1
Severity: normal
File: wacom
Hi,
This report is a result of an investigation into weird tablet behaviour using
Krita and other Qt tablet software: https://bugs.kde.org/show_bug.cgi?id=184485
I'm running most packages from testing, except wacom packages from unstable,
and a whole bunch of KDE 4 stuff from experimental. I've been experiencing the
symptoms of this problem for some months, but I think I've finally got a
handle on its source.
The function xf86WcmDevConvert in xf86Wacom.c should be automatically called by
the Xorg server to translate from the device-space coordinates to screen
coordinates. There exists workaround code in the wacom driver that is disabled
when compiled against recent Xorg versions, as older Xorg versions did not
automatically call the conversion function (apparently).
However, when I run Xorg with Option CommonDBG 6 it's clear that
xf86WcmDevConvert is never called. When I compile the package from source (i.e.
dpkg-buildpackage), it's clear that the workaround is not being compiled in,
either.
This only affects core events, and doesn't effect software which does its own
conversion from raw tablet data. Presumably, this is why symptoms only appear
when using Qt, just because of the (I guess, unusual) way it disects tablet
events.
Peace,
Brendon
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (102, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-input-wacom depends on:
ii xserver-xorg-core 2:1.4.2-10 Xorg X server - core server
xserver-xorg-input-wacom recommends no packages.
Versions of packages xserver-xorg-input-wacom suggests:
ii wacom-tools 0.8.1.6-1 utilities for Wacom tablet devices
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Feb 22, 2009 at 05:10:03PM +1000, Brendon Higgins wrote:
> Package: xserver-xorg-input-wacom
> Version: 0.8.1.6-1
> Severity: normal
> File: wacom
>
>
> Hi,
>
> This report is a result of an investigation into weird tablet behaviour using
> Krita and other Qt tablet software:
> https://bugs.kde.org/show_bug.cgi?id=184485
>
> I'm running most packages from testing, except wacom packages from unstable,
> and a whole bunch of KDE 4 stuff from experimental. I've been experiencing the
> symptoms of this problem for some months, but I think I've finally got a
> handle on its source.
>
> The function xf86WcmDevConvert in xf86Wacom.c should be automatically called
> by
> the Xorg server to translate from the device-space coordinates to screen
> coordinates. There exists workaround code in the wacom driver that is disabled
> when compiled against recent Xorg versions, as older Xorg versions did not
> automatically call the conversion function (apparently).
Scaling in the xorg input system got fairly badly broken for a while,
hopefully most of those issues will be solved for the 1.6 release, but
in the meantime, there's not much we can do about that now in existing
stable releases.
> However, when I run Xorg with Option CommonDBG 6 it's clear that
> xf86WcmDevConvert is never called. When I compile the package from source
> (i.e.
> dpkg-buildpackage), it's clear that the workaround is not being compiled in,
> either.
It should be clear why if you have a look at http://bugs.debian.org/495002
> This only affects core events, and doesn't effect software which does its own
> conversion from raw tablet data. Presumably, this is why symptoms only appear
> when using Qt, just because of the (I guess, unusual) way it disects tablet
> events.
So empirically, the obvious conclusion is that Qt is wrong :)
I'm closing this as a bug report against this package, because I don't
really see an issue in it that we could attach it to. You could reassign
it to some more appropriate part of Qt, but probably the best thing to do
is get Qt/KDE upstream talking directly to linuxwacom upstream (who've
already been talking to xorg upstream), and get them all on the same page
about how to deal with this in which versions of what.
The linuxwacom discuss or devel list is probably a good place for that.
6 months ago was probably a good time for it, but it's never too late
to make a new start.
Cheers,
Ron
--- End Message ---
