Cursor freeze with Wacom Graphire3 & Graphire4 on Windows

[Bug Importer]

- 0.45.1 on WinXP SP2
- No mouse ony Wacom Graphire3
- Cursor freeze when Inkscape starts and application has focus
- If focus changes cursor is available again

[John Cliff (johncliff)]

Can you confirm that this is still an issue in a current SVN build.
Can you confirm the tablet works with GIMP?
Can you provide some contact details as this is a fairly setup dependant problem.

[Chris Lambacher (chris-kateandchris)]

I am also having this problem 0.45.1 on WinXP SP2. I also tried I updating the gtk libraries to 2.10.13 (installer from http://gimp-win.sf.net/). I updated inkscape to Inkscape0712281743.7z from the nightly builds. Same problem.

GIMP for Windows (version 2.4.2) from http://gimp-win.sf.net/ also has issues, but I am not seeing the exact same behaviour.

Here is a more detailed description of the behaviour:
  - The pen in absolute position mode works
  - If the mouse is set in absolute position mode, the cursor can get stuck, but taking it on and off the tablet a few times the cursor will start to move again.

  - The pen in relative position mode moves the cursor, but Inkscape interprets the position as if it it were in absolute mode
  - The tablet mouse in relative position mode never moves the cursor, but is interpreted as being in absolute position as indicated by the ruler guide markers (can't see the cursor, but can see the guide markers move.)

  - The right click context menu does not pop up with either the mouse or the tablet.

The right click problem is fixed in Inkscape0712281743.7z

Summary, relative mode is broken, absolute mode mostly works.

[Subvertio (sdfavis)]

Yes, I am having the same issue as John and Chris. I have had the exact same issue on multiple PC's, XP x64, and XP 32...

Cursor just stops responding in tablet mode / and in mouse mode for Graphire 3 tablet. I toyed with changing acceleration from tablet software, when it is OFF it is non-functional, but when it is on lowest setting it seems to work longer, then stops responding.

Other than that the program is awesome!

[David Császár (p5)]

duplicate of Bug #168819 (same problem with graphire 4)

[Tom Davidson (tjd-mit)]

At bug 168819, this same behavior was reported using the graphire4 on WinXP, XP SP2, and Vista. I merged it in as a dupe per David's suggestion. Some comments of interest from that thread:

"What I have found is that when I
lift the pen from the tablet it unfreezes much faster than when I keep the
pen near the tablet. I have a mouse plugged in at the same time, and if I
try to move the mouse it moves the cursor like normal."

"If the stylus moves out of range of the tablet (ie. too high) the mouse
pointer freezes.
The frozen pointer may be recovered by:
* Using the mouse
* Moving the stylus in at a low level from the edge of the tablet
This is also and issue with the latest version of GIMP (version 2.4.1)..."

The fact that it is an issue in GIMP makes it sound like a GTK problem, rather than an Inkscape problem...

[Samuel S. Weber (ssweber)]

Solution: Download the 4.97-6 driver (http://www.wacom.com/productsupport/download.cfm?id=161&product=CTE4)
Uninstall newer tablet driver.
Install normally in Windows XP.

For Vista, you will have to disable UAC temporarily. Go to -> Control Panel -> User Accounts -> Turn User Account Control On or Off -> Then uncheck the box. No need to restart. Try to install. It will say "Platform not supported". When you close the dialog a Windows Dialog will pop up and say something about correct settings (maybe it turns XP compatibility on?). Click "Retry install". It should work now.

-Sam

[keldon85 (keldon85)]

I'm getting the same problems with my Wacom Bamboo; I'm using XP Pro and the latest drivers for the Bamboo (taken from the website).

Unfortunately this may never be resolved under Windows, see ( https://bugs.launchpad.net/inkscape/+bug/178823/comments/1 ). Seems to be a common GTK+ / Wacom bug -_-

[Voon (skygazing)]

The freezing problem can be patched. The patching instructions are described here by Thomas Bleeker: http://bugzilla.gnome.org/show_bug.cgi?id=496958.

I've tried it and works great for me. I've also attached the patched DLL file for download here: https://bugs.launchpad.net/inkscape/+bug/178823/comments/3

[sas (sas-sas)]

This bug should be fixed in the latest development builds, available from http://inkscape.modevia.com/win32/?C=M;O=D

[Granjow (simon-eu)]

How come that this problem still exists in 0.46?

[Granjow (simon-eu)]

Edit: I've seen that in the current dev release this problem is fixed too, also for the newest available Wacom driver.

[goto (gotolaunchpad)]

I updated my Wacom driver to version 5.08-2 and have that freezing cursor-bug now too. I didn't have that problem with my old driver version.

(WinXP SP3)

[goto (gotolaunchpad)]

Someone better mark this bug as important, as Inkscape does not work at all and lies on a hard drive completely unusable.

[kddesigns (kellysdigitaldesigns)]

I downloaded the newest version and the curser freezes when I use my Wacom tablet.

[Locked (info-locked)]

I'm running Inkscape 0.46 and also have a major problem with my Wacom Bamboo:
one way to reproduce the problem now about 10 times was:
- Start Inkscape,
- change the input device to "WACOM Tablet Eraser" (2nd from top), use the keyboard to save and close the dialog
- pen works
- move the mouse
- try to continue with the pen - the cursor just jumps araound :-(
- then I have to change the input device back to "WACOM Tablet Eraser" (2nd from top) as it is changed back to "Wacom Tablet Pressure Stylus"

it drives the tablet absolutely unsuable.

[johnc (johnc-ayanova)]

Forget it guys. It's been over two years now, clearly this will never be fixed, there is little point in pursuing this anymore. Buy a different tablet or whatever but let's just stop pinning any hopes here right now ok? :)

[Locked (info-locked)]

And hope that other tabblets keep working? Maybe just search an alternative editor :-(
I'd already be happy if the input device wouldn't change automatically. Just FORCE it to a specific setting if needed.

[madwizard (thomas-madwizard)]

Have you tried my patch?

[Niko Kiirala (kiirala)]

As noted by Voon ans sas, this problem has been fixed. I'll change the bug status to avoid any further confusion. Please try a recent development build or the patch that has been provided for 0.46. If the given solutions don't work, feel free to reopen this bug.

To Locked: the input device dialog is meant just to configure the input devices, it won't select the used device. To use the 'eraser' device, turn you stylus upside-down.

[Locked (info-locked)]

I did not use the eraser setting in order to use the pen as an eraser. But this was the only method to make the tablet working at all (for a short time). At home I'll try a nightly build - mabye it helps.

[Locked (info-locked)]

Wow! The nightly build Inkscape21627-0906200405.7z seems to work with my Wacom Bamboo!
Just tested it some minutes - no jumping of the cursor.

[oxk4r (oxk4r)]

Yes, but it only works deactivating the pressure sensibility option in the Preferences/Mouse. At least in my case. Anyway, it's a great step.

[Ola Lindberg (olalindberg)]

I'm also having problems with Wacom and GTK. I'm running all my GTK apps with the "--no-wintab" options.
It makes it work, but it looses the pressure sensibility.

[keldon85 (keldon85)]

I just can't take this application seriously; Wacom is the most important
tablet vendor to support and it's been an unresolved issue for years. It's a
great vector editor, but without Wacom tablet support it's next to useless!
That's not to say that the work is not appreciated, but this should be the
highest priority job to fix if this project is to be taken *even
remotely*seriously.

Cheers,

KA

2010/1/5 Ola Lindberg <email address hidden>

> I'm also having problems with Wacom and GTK. I'm running all my GTK apps
> with the "--no-wintab" options.
> It makes it work, but it looses the pressure sensibility.
>
> --
> Cursor freeze with Wacom Graphire3 & Graphire4 on Windows
> https://bugs.launchpad.net/bugs/168646
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
- Keldon Alleyne