Jason Gerecke

Looks like there's no USB traffic being sent by the 24HD at all after the issue is triggered. Still not sure of the actual trigger of if its a driver...

That would make sense, though I'm somewhat skeptical that a kernel change is the actual cause of the problem (as opposed to merely triggering an existing problem). My 24HD has...

Can you please run our [sysinfo.sh script](https://raw.githubusercontent.com/linuxwacom/wacom-hid-descriptors/master/scripts/sysinfo.sh) with the 22HD connected and attach the generated tarball to this issue?

Can you please try to trigger the issue, and once it occurs immediately open a terminal and run `sudo journalctl --since="5 minutes ago" > error.log` for us? Attach the error.log...

Can you confirm that the 27 still works properly in 16.04 if you boot it up in a live environment? If your problem is the same as #34 I would...

That _is_ really weird... I guess there could be something in userspace that is causing a problem. I wonder if e.g. fwupd could be to blame? The missing touch device...

Thanks for the script! I'll have to give that a shot on my 24HD if/when it stops working again to see if your bind/unbind can work for both devices.

Just got [another report](https://twitter.com/artredj/status/1193511701888589825) of this issue affecting a 27QHD user with a 5.x kernel. I've also been able to confirm that using the bind/unbind method on the USB port...

Ran `git bisect` on a Fedora 27 machine and got torvalds/linux@e04a0442d33b8cf183bba38646447b891bb02123 as a commit of interest. ~~~ $ git bisect log git bisect start # good: [569dbb88e80deb68974ef6fdd6a13edb9d686261] Linux 4.13 git...

Also: I'd noticed early on in debugging that running `rmmod wacom` and then `modprobe wacom` would cause the device to disconnect (as expected) but never come back until I either...