Open stuarthayhurst opened 1 year ago
https://github.com/linuxwacom/input-wacom/issues/335 The issue where after a while the whole wacom driver colapses is still happening
Added, thanks
I will add that my Lenovo E-Color Pen is also not detected after sleep. I can only draw after first boot.
I will add that my Lenovo E-Color Pen is also not detected after sleep. I can only draw after first boot.
Is that reported anywhere?
No, its personal experience only.
Ok cool, feel free to link to an issue if you report it
Lenovo E-Color Pen has bad support and doesn't show up in GNOME Wacom Tablet settings. Probably missing something in the driver, but I am unsure of what that is right now.
Of note here only the display shows up even when using the pen.
$ libwacom-list-local-devices
devices:
- name: 'Wacom HID 52D3'
bus: 'i2c'
vid: '0x056a'
pid: '0x52d3'
nodes:
- /dev/input/event11: 'Wacom HID 52D3 Pen'
@stuarthayhurst You have a different screen than me. Do you have the Pen showing up in GNOME or in libwacom-list-local-devices
? I might need to make a definition for mine since it's such a unique pen.
On a fresh boot without bringing the pen (Lenovo Active Pen 2) to the screen yet, I get
devices:
- name: 'Wacom HID 52D5'
bus: 'i2c'
vid: '0x056a'
pid: '0x52d5'
nodes:
- /dev/input/event3: 'Wacom HID 52D5 Pen'
After bringing the pen to the screen, I get the same result
With or without bringing the pen to the screen, it shows up in GNOME Settings (I think it started doing this after we added the entries for the screens to libwacom)
My Lenovo E-Color Pen doesn't show up, but does work correctly.
Add any issues with the pen / touchscreen to this issue, I'll add them to the list :)
Fixed:
libwacom
is unaware of the digitiserupower
identifies the screen as a keyboardupower
registers a non-existent batteryReported:
input-wacom
) crashes randomlyUnreported: