Bug 196673 - wacom driver misbehaves
Summary: wacom driver misbehaves
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-16 01:28 UTC by Hrvoje Zeba
Modified: 2017-08-17 16:04 UTC (History)
4 users (show)

See Also:
Kernel Version: 4.12.6-1-ARCH
Subsystem:
Regression: No
Bisected commit-id:


Attachments
part of dmesg output (4.51 KB, text/plain)
2017-08-16 01:28 UTC, Hrvoje Zeba
Details
lsusb output (341 bytes, text/plain)
2017-08-17 16:01 UTC, Hrvoje Zeba
Details

Description Hrvoje Zeba 2017-08-16 01:28:40 UTC
Created attachment 257929 [details]
part of dmesg output

Hi!


I have a Lenovo Yoga X1 2nd gen system (20JD) with touchscreen/pen support running arch linux. The issue is that after a few cycles of write on the screen with a pen and use the touchscreen with my fingers, the drivers goes haywire. By haywire, I mean the pen starts emitting a button press when the pen comes close to the screen on it's own and touchscreen stops tracking finger movements. Plain touch more or less still works. I've attached relevant dmesg output which happens around the time the driver starts acting up. Also, both buttons are reported as one and battery status is not read correctly. I've confirmed that both the pen and the touchscreen work correctly in windows.


I'd like to help debug this problem, if that's ok.


Thank you,


Hrvoje Zeba
Comment 1 Hrvoje Zeba 2017-08-17 16:01:05 UTC
Created attachment 257997 [details]
lsusb output
Comment 2 Hrvoje Zeba 2017-08-17 16:04:25 UTC
I've added lsusb output and figured out that the traceback in dmesg appears only after I try to remove the wacom module. When I reinsert the module, everything goes back to normal for a while.

Note You need to log in before you can comment on or make changes to this bug.