<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Huion DWH69 not working with libinput 1.4.2 and xf86-input-libinput 0.19"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97771#c38">Comment # 38</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Huion DWH69 not working with libinput 1.4.2 and xf86-input-libinput 0.19"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97771">bug 97771</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>(In reply to ngoonee from <a href="show_bug.cgi?id=97771#c29">comment #29</a>)
<span class="quote">> libinput error: libinput bug: Device 'PenTablet Keyboard' does not meet
> tablet criteria. Ignoring this device.</span >
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
<span class="quote">> 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?</span >
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 <a href="show_bug.cgi?id=97771#c37">comment #37</a>)
<span class="quote">> Based on <a href="https://github.com/DIGImend/digimend-kernel-drivers/issues/10">https://github.com/DIGImend/digimend-kernel-drivers/issues/10</a> I
> figured that it really should be possible to use this tablet with libwacom,</span >
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.
<span class="quote">> 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. </span >
if xsetwacom detects the device you assigned the wacom driver, not libinput.
change the Driver line to "libinput".
<span class="quote">> 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.</span >
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?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>