After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 166397 - GTK apps won't return from tablet to mouse input
GTK apps won't return from tablet to mouse input
Status: RESOLVED NOTGNOME
Product: gtk+
Classification: Platform
Component: Backend: X11
2.4.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-02-05 22:06 UTC by quazgar
Modified: 2005-04-07 06:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description quazgar 2005-02-05 22:06:02 UTC
Version details: 2.4.14
Distribution/Version: Gentoo

I've problems with an Aiptek 12000U tablet, when using GTK applications.

The problem is (in GIMP and in testinput from the GTK-testing tools as well):
Once I use the tablet pen (which works very fine, as it should), the application
won't recognize the (normal) mouse as the CorePointer again but rather as my
tablet pen, but without the possibility to send button events. It just moves the
cursor around. The mouse continues to work alright in other X applications.

I am running on gentoo, Kernel 2.6.10, xorg, GTK+ 2.4.14 and the latest driver
from aiptektablet.sourceforge.net, the "xinput test pen" test program indicates
that the tablet integration into X seems to be working.

Steps to reproduce the bug:
- Start X with support for the Aiptek tablet (appropriate InputDevice and
ServerLayout sections in XF86Config/xorg.conf).
- Start the Gimp or the GTK testinput program and configure it to recognize the
tablet device.
- Paint something with the mouse, the tablet pen and with the mouse again.

Expected results:
Should paint with both devices.

Actual results:
Will paint normally with the mouse first, the as expected with the pen but will
refuse to paint with the mouse again afterwards.
Comment 1 Owen Taylor 2005-02-06 04:49:05 UTC
Almost certainly a driver bug. Sounds like your tablet is sending a ProximityIn
but no ProximityOut.
Comment 2 quazgar 2005-02-06 11:24:50 UTC
@ Owen Taylor: Might well be, "xinput test -proximity pen" doesn't show any
ProximityOut events. I will try to have a look at the driver, maybe the Aiptek
driver people know more. It would be ok for me to close this bug as
Needinfo/Wontfix until I know more about the proximityIn/Out thing...