Tablet input resolution tied to display resolution

Bug #195953 reported by Tom Jaeger
18
Affects Status Importance Assigned to Milestone
wacom-tools (Ubuntu)
Fix Released
High
Timo Aaltonen
Nominated for Hardy by Vincenzo Ciancia

Bug Description

Binary package hint: wacom-tools

Stroke quality in apps like xournal or gimp has been really low ever since the switch to xserver 1.4. The underlying issue was recently fixed in xserver git master (see http://bugs.freedesktop.org/show_bug.cgi?id=10324 ), and, amazingly, the patches have made it into debian/ubuntu shortly afterwards. So the only outstanding issue is in the wacom X input driver, which is still reporting low-resolution events to the X server. Just removing the sections described as "Ugly hack for xorg 7.3" won't solve the issue (the mouse pointer is confined to a small rectangle in the upper left corner of the screen), but fortunately the latest linux-wacom git has full support for high-resolution events again. Here's how it can be compiled:

git clone git://git.debian.org/git/collab-maint/linux-wacom.git
cd linux-wacom/
./bootstrap
./configure --disable-quirk-tablet-rescale
make
# install using
# sudo cp -b src/xdrv/wacom_drv.so /usr/lib/xorg/modules/input/

Please bump up the importance of this bug since it makes Tablet PCs all but unusable on hardy.

Revision history for this message
Tom Jaeger (thjaeger) wrote :
Iulian Udrea (iulian)
Changed in wacom-tools:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

See also the full explanation of the problem given by the upstream developer of Xournal, Denis Aurox:

http://sourceforge.net/tracker/index.php?func=detail&aid=1891727&group_id=163434&atid=827733

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

I confirm that new release of linux-wacom solves the problem. I also have to enable "discard core events" under xournal, but that's a xournal-specific issue. This fix is absolutely necessary for hardy.

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Can someone please explain what needs to happen for this to be fixed? This is really just a new upstream release (0.7.9-8) that needs to be packaged. Do we need to wait for debian first? Should someone bug the debian maintainer about this?

Revision history for this message
Christian Reis (kiko) wrote :

Tom: it'll be a good idea to bug the debian mantainer so he does the packaging, but you can get somebody to package it for Ubuntu if you are in a hurry. You'll then need to request a UVFE for it, since we're already in UVF.

Revision history for this message
Daniel Hahler (blueyed) wrote :
Changed in wacom-tools:
status: Confirmed → Triaged
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I've tried to compile it a couple of times in the past but it fails, and don't know the package well enough to fix it...

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Timo,
I took me a while, but I got it to compile now. My focus was on getting it to work, I don't have the necessary experience to build a proper package. Applying the wacom-tools_0.7.9.3-2ubuntu2.diff.gz patches to the lastest linux-wacom yielded a few failed hunks, but they were all trivial to fix or applied already. There were two remaining issues:

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Sorry about that, my keyboard stopped working all of a suddon (this is hardy, after all).
The issues were:

* The scaling quirk needs to be disabled in configure.in (I replaced the test starting at line 444 with "WCM_TABLET_SCALING=no"). Of course, a bootstrap is needed afterwards.

* There were Makefile issues in src/xdrv, basically some include directories needed to be fixed (I don't understand why debian makes everybody's life harder by using separate build directory implemented in this way). I don't know how to do this properly (and I could care less, I really hate autokludge, ), so I just edited Makefile.in. I've attached my version of it.

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Okay, I redid the whole thing. I also moved my changes to Makefile.am, so that bootstrap won't overwrite them. The changelog still needs to be updated and the version number needs to be bumped, I'll leave that to someone who knows ubuntu policies better than I do.

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Timo, not good enough?

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

Importance should be high, not medium. Please take care of this bug, it breaks functionality and there is a fix.

Revision history for this message
Tom Jaeger (thjaeger) wrote :
Revision history for this message
Tom Jaeger (thjaeger) wrote :

Can somebody please take care of this?

Revision history for this message
Murat Gunes (mgunes) wrote :

Tom, please provide all the information specified in https://wiki.ubuntu.com/FreezeExceptionProcess#head-30ede7e753a6b6f62916161755507d4cc5d99e20 and subscribe ubuntu-main-sponsors afterwards. Also, your debdiff doesn't look good; it's 3.4 megabytes.

Revision history for this message
Tom Jaeger (thjaeger) wrote :

I removed some autogenerated garbage from the "original tarball" (0.7.9.3 did the same thing), that shrinks the debdiff down to 1.3M.

Revision history for this message
Tom Jaeger (thjaeger) wrote :
Revision history for this message
Tom Jaeger (thjaeger) wrote :
Revision history for this message
Tom Jaeger (thjaeger) wrote :
Revision history for this message
Tom Jaeger (thjaeger) wrote :

* removed some left-over documentation from the linuxwacom directory. Everything in the debdiff now is an upstream change or the result of running ./bootstrap

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Sorry, leftover docs/ directory in the "original" tarball.

Revision history for this message
Tom Jaeger (thjaeger) wrote :
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Tom: sorry for not noticing your work before! I'll check out the package and upload it. We really need this version, upstream agrees that it's the first version to work correctly with xserver 1.4.

Timo Aaltonen (tjaalton)
Changed in wacom-tools:
assignee: nobody → tjaalton
status: Triaged → In Progress
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Ok, the package is now uploaded and waiting. The version number was wrong, this is -0ubuntu1 since Debian doesn't have it yet, and I added some documentation about the changes. Wacom.templates remained untouched, since we are in string freeze and it's unnecessary delta imho.

Changed in wacom-tools:
status: In Progress → Fix Committed
importance: Medium → High
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Oops, apologies for not realizing that since the archive is not frozen new package versions are accepted automatically. So the package is now in the archive and this bug can be closed.

Changed in wacom-tools:
status: Fix Committed → Fix Released
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

is it possible that the updates broke it for me? I get xorg saying it couldn't open module wacom.

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Thanks, Timo. This is greatly appreciated.

Jean-François is right, this package builds wacom_drv.o instead of wacom_drv.so. Absolutely no idea why; all I did since the last version I tested this with was remove a few directories. Anyway, a simple ./bootstrap in linuxwacom fixes this.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Yep, I've fixed that with -0ubuntu2.

Revision history for this message
morinpatmorin (morinpatmorin) wrote :

> Yep, I've fixed that with -0ubuntu2.

Um. I don't think so. I just installed

http://security.ubuntu.com/ubuntu/pool/main/w/wacom-tools/xserver-xorg-input-wacom_0.7.9.8-0ubuntu2_i386.deb

and this file is still in there:
usr/lib/xorg/modules/input/wacom_drv.o

Pat

Revision history for this message
Tom Jaeger (thjaeger) wrote :

I think this is the issue (from linuxwacom/configure):

if test "$WCM_OPTION_DLLOADER" = yes; then
        if test -f $WCM_MODDIR/evdev_drv.so -o -f $WCM_MODDIR/kbd_drv.so -o -f $WCM_MODDIR/mouse_drv.so; then
                WCM_OPTION_DLLOADER=yes
        else
                WCM_OPTION_DLLOADER=no
        fi
fi

So we should either remove that test or add xserver-xorg-input-kbd to build-depends.

Sorry about that. I'm setting up a pbuilder environment right now to test my hypothesis...

Revision history for this message
Tom Jaeger (thjaeger) wrote :

Yup, that was it.

Revision history for this message
morinpatmorin (morinpatmorin) wrote :

Thanks for the quick response and update Tom. Everything's working fine on my x61 and the stroke quality has definitely improved in Jarnal.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.