wacom kernel driver ends up in non-working state after first unplug

This is similar to, but not the same as, bug #511844, which was an X input bug with similar symptoms.

`modprobe -r wacom` after unplugging the tablet doesn't seem to be sufficient to reset things either

Note that wacom-tools aren't currently installed either, so this is a pure kernel-wacom-driver bug:

wacom-tools:
  Installed: (none)
  Candidate: (none)
  Version table:
     1:0.8.4.1-0ubuntu4 0
        100 /var/lib/dpkg/status

Ah, it seems wacom-tools are obsolete anyway.

Also:
lsb_release -a:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04 LTS
Release: 10.04
Codename: lucid

The Xorg side of things seems to be working okay (and we've proven that the problem is on the kernel side using evtest above), so all that should really be necessary to check for the existence of the bug is the following:

1) with the tablet plugged in (the first time), run `xinput list` to find out the tablet's device ID (look for the entry without "eraser" or "cursor")
2) run `xinput test ID`, where ID is the ID from
3) observe that scribbling on the tablet generates input events
4) unplug the tablet
5) observe that `xinput list` no longer lists the tablet
6) plug it back in
7) observe that the tablet is back with `xinput list` (normally it will get the same ID again, but check)
8) run `xinput test ID` again, and observe that scribbling on the tablet no longer generates events

My Intuos 2 6x8 has this problem, may be worth seeing whether it is an issue with other tablet models

Bus 005 Device 011: ID 056a:0042 Wacom Co., Ltd Intuos 2 6x8

Also:

mental@bede:/sys/module/usbcore$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04 LTS
Release: 10.04
Codename: lucid

Did a test here with Intuos3 6x11:

Ubuntu 10.04 amd64

"xinput list" shows the devices. "xinput test" showed data. Unplugged, issued another "xinput list" and the device was removed from the list. A subsequent plugging in and "xinput test" worked as expected.

Hi Tim,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 597123

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Had the same non-working state issue with my Intuos 2 6x8.

Tried with mainline kernel; hotplugging the device still doesn't work, though strangely enough I do get events reported by evtest, but still not xinput. Similar results with the livecd, though I wasn't able to run evtest because it's not included.

So, so far I've only heard/seen problems with Intuos 2 specifically. I wonder if it has to do with the way the device is initialized by the driver on hotplug.

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]