Wacom tablet stops working after hibernation

[Simon Woolf]

After hibernating and resuming, my Wacom (Volito2, CTF-420) tablet does not work. It continues not to work even after restarting X; a reboot is needed to make it work again.

Running Ubuntu 9.04, with wacom-tools and xserver-xorg-input-wacom both at version 1:0.8.2.2-0ubuntu2.

[Eiríkr Útlendi (erikanderson3)]

Same exact problem. Very disruptive, as my Wacom tablet is my only mouse device. Any news/progress?

[Eiríkr Útlendi (erikanderson3)]

Addendum --

Wacom tablet Intuos, model PTZ-930
Ubuntu version 9.04
xserver-org-input-wacom version 1:0.8.2.2-0ubuntu2
wacom-tools --> not installed, actually. I've just been using the default config that came with a fresh Jaunty install (i.e., *not* an in-place upgrade).

I'll try installing wacom-tools and see if hibernation works any better.

[Eiríkr Útlendi (erikanderson3)]

No dice. Both suspend and hibernate result in a dead Wacom tablet, with or without wacom-tools installed. The light indicators on the tablet are still shining, showing that the device still gets power and some kind of signal, but X seems to be ignoring any input. I scrounged an old USB mouse, and that still works, but the tablet is ignored completely. A hal issue? I'll see later if xev registers anything.

[jorno (jorn-odberg)]

I have a similar problem, on my HP Pavilion TX2690 TabletPC.

After hibernation, the stylus and eraser is out of calibration. (at the left of my screen, it matches... when I move it towards the right, the speed is about 200%, so when my pen is at the middle of the screen, the pointer is to the far right.)

But the funny thing is: The "Touch" is correct (me pointing at the screen). It's just the Stylus and Eraser which is off.

Please tell if I should include some more info!

Kind regards from Norway,
Jørn.

[Henri Sivonen (hsivonen)]

Still happens on Karmic with Wacom Graphire 2.

[Bryce Harrington (bryce)]

Thank you for reporting this issue with wacom-tools, we are migrating it to the new xf86-input-wacom package which has replaced it in the development version of Ubuntu.

This would be a good point for you to re-test this issue against the new package to see if is still occurring. If not, you can mark it as Fix Released in Launchpad. If it is still an issue in the current development release and you're the original reporter, please reply and attach a fresh Xorg.0.log.

[madbiologist (me-again)]

A patch titled "Input: wacom - switch mode upon system resume" is included upstream in the kernel's linux-next integration testing tree. This patch has also been cc'd to the maintainers of the stable kernels (2.6.33 and possibly 2.6.32).

Full details are at http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=014f61504af276ba9d9544d8a7401d8f8526eb73

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Simon,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 395537

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 395537 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/395537

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.