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 162803 - mouse slows down
mouse slows down
Status: RESOLVED DUPLICATE of bug 163163
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.4.x
Other Windows
: Normal normal
: Need diagnosis
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-01-03 12:17 UTC by Luke Schierer
Modified: 2005-02-03 01:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luke Schierer 2005-01-03 12:17:56 UTC
Lee Jackson (ljfnord at users dot sf dot net) reports
" Ever since v1.0.3 came out, I've had a problem with the
mouse cursor. When any WinGaim window has the focus,
the mouse moves very slowly. When I switch focus away
from WinGaim (but leave it running), it resumes normal
speed. Closing WinGaim also sets the mouse speed back
to normal. I'm not doing anything special to get this
to happen - it's the default behaviour, unfortunately,
and version 1.1.0 didn't solve the problem.

Here are my system specs:

OS: WinXP SP2 w/all current updates
Mouse: Wacom Graphire2 pad (USB, in mouse mode) (driver
v4.78-6)
MB: Leadtek 7350KDA
CPU: Athlon XP 1800+
RAM: 1GB (2x512MB)
Video: RADEON 9550 (128 MB)"

after asking him to test this with gimp,
"I downloaded the latest GIMP and GTK 2.4.14 and installed
both.  I get the same slowdown in the GIMP that I do in
GAIM, so you're right - it's probably a GTK issue.  I'm
using the latest Wacom drivers, so I'm at a loss as to how
to solve this."
Comment 1 Robert Ögren 2005-01-14 23:17:01 UTC
Since GTK+ currently always initializes Wintab tablet support, it initializes it
when Gaim starts. For some reason the mouse/puck speed changes when Wintab is
initialized, it happens to me too (though I don't normally use mouse mode with
the tablet, I use a real mouse instead). For Gaim this should be solved if/when
we implement lazy Wintab initialization as Owen suggested in bug #162334. Apart
from that I don't think there is anything simple we can do in the Wintab code in
GTK+ to make the speed match, it uses default values provided by the tablet
driver as far as I can see.

Please see the workarounds described in bug #162334 for disabling wintab
initialization.
Comment 2 Tor Lillqvist 2005-02-03 01:21:39 UTC
Since lazy Wintab initialization is now in, this can presumably be resolved as a
dupe of the bug with the lazy initialization fix.

*** This bug has been marked as a duplicate of 163163 ***