<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c39">Comment # 39</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 <a class="email" href="mailto:ngoonee@gmail.com" title="ngoonee@gmail.com">ngoonee@gmail.com</a> <pre>(In reply to Peter Hutterer from <a href="show_bug.cgi?id=97771#c38">comment #38</a>) > (In reply to ngoonee from <a href="show_bug.cgi?id=97771#c29">comment #29</a>) > > 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 Nope, at least not that I've set myself. And this being Arch, unlikely to have much non-upstream defaults anyway. > > 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. Will get round to that soon. > > 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? So I tested with Driver line to libinput (and restarted, otherwise it kept using libwacom), and the stylus itself works but I lose the frame buttons as compared to when I was using 'wacom'. Doesn't even show up in xev. Behaviour in gimp/inkscape is unchanged compared to wacom. I can scroll fine (using my mouse) until I first draw something, after which no scrolling will work until I unplug the tablet.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>