Barrel button/pen input conflict (Huion Kamvas Pro 16, 2019 model)

Support
6

I’ll ignore that for now …

Only if you did something that goes against the default configuration files and driver.
Share the content of the files that have tablet and/or wacom in their name from:
/usr/share/X11/xorg.conf.d/
and
/etc/X11/xorg.conf.d/

In principle you should see something like this if you indeed used the digimend with xsetwacom functionality :

Section "InputClass"
    Identifier "Huion on wacom"
    MatchProduct "HUION"
    MatchDevicePath "/dev/input/event*"
    Driver "wacom"
EndSection

I’ll give you an example of why that should be not possible, from my end The stylus has an ID that can be also seen with the use of xinput

xinput list
⎜   ↳ Wacom Cintiq 22HD Pad pad                 id=12   [slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 22HD Pen stylus              id=13   [slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 22HD Pen eraser              id=14   [slave  pointer  (2)]

With that ID i can see the props for it and in this case is id=13 … so:

xinput list-props "13"
        Wacom Button Actions (654):     "Wacom button action 0" (655), "Wacom button action 1" (656), "Wacom button action 2" (657), "None" (0), "None" (0), "None" (0), "None" (0), "Wacom button action 3" (658)
        Wacom button action 0 (655):    1572865
        Wacom button action 1 (656):    1572866
        Wacom button action 2 (657):    1572867
        Wacom button action 3 (658):    1572872

even tho the props is longer, i focus only on the buttons part, and even tho i did not mentioned it previously, it includes the eraser tip too, and also the numbering goes like this compared to the UI settings
button action 0 is button 1 in UI
button action 1 is button 2 in UI
button action 2 is button 3 in UI
button action 3 is the eraser tip i did not mentioned before but has the settings …

Now, the action number is different for each, as you can see, and even tho is not the same number for the event, each should be totally different by default. All documented in the libinput (that are used by all drivers)

Emphasis on the unrelated and the reason for that is to avoid a situation like yours, reason why i had to make sure what you say is really the case. If not the config files are the reason for your issue, then the only valid an logical possibility is a faulty Stylus.

1 Like