https://bugs.freedesktop.org/show_bug.cgi?id=97771

--- Comment #38 from Peter Hutterer <peter.hutte...@who-t.net> ---
(In reply to ngoonee from comment #29)
> libinput error: libinput bug: Device 'PenTablet Keyboard' does not meet
> tablet criteria. Ignoring this device.

This message means that the device has ID_INPUT_TABLET assigned but it
shouldn't. That's a udev issue, not sure why this happens though. Do you have a
manual override or something? same for th eothers

> libinput error: libinput bug: Device 'PenTablet System Control' does not
> meet tablet criteria. Ignoring this device.
> libinput error: libinput bug: Device 'PenTablet Consumer Control' does not
> meet tablet criteria. Ignoring this device.
> libinput error: libinput bug: Device 'PenTablet Mouse' does not meet tablet
> criteria. Ignoring this device.
> event16 DEVICE_ADDED     PenTablet Pad                     seat0 default
> group10 cap:P buttons:8 strips:0 rings:0 mode groups:1
> event15 DEVICE_ADDED     PenTablet Pen                     seat0 default
> group10 cap:T  size 229.30/143.31mm
> 
> I assume this means the patch applies successfully at least?

yes, P and T are Pad and Tablet capabilities. and from the evemu output at
least I can tell that the event sequence looks correct. libinput spits out a
whole bunch of tablet events too.
I recommend grabbing libinput from git and building with gtk+-3 devel headers
installed. that way you can run make and sudo ./tools/event-gui to test if the
tablet responds correctly.


(In reply to ngoonee from comment #37)
> Based on https://github.com/DIGImend/digimend-kernel-drivers/issues/10 I
> figured that it really should be possible to use this tablet with libwacom,

libwacom is merely a descriptive library. it's used by GNOME but only to
display the config item. It doesn't decide if the tablet works otherwise.

> and simply adding a 'PenTablet' MatchProduct to my xorg.conf (specifically I
> edited /etc/X11/xorg.conf.d/70-wacom.conf) means xsetwacom picks up my
> tablet. 

if xsetwacom detects the device you assigned the wacom driver, not libinput.
change the Driver line to "libinput".

> The lack of proximity out of range event has a pretty annoying sideeffect
> that I can't scroll in gimp/inkscape as the button4/5 events don't seem to
> do anything.


from the libinput output I get here you get proximity events. there's a tip up,
followed by axis events (though it doesn't move much) so proximity works. the
stylus buttons come in while the tip is up, so everything appears to work?

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

Reply via email to