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

Support
8

Is clear what i stated:

Reason why i asked to share them, and:

I never insinuated by any words that you make things up. Is the second time you actually are the one pretending of “reading my mind” and accusing me of not doing, or doing something that for you is not nice.
Seriously?

I come as a Manjato Team member, then as a user
You can use xsetwacom only because once you make the huion driver to use it, your tablet becomes as a wacom device, reason why you get

in your xinput.

There is the problem then, as is guessed the first time. Let me remind you

When you install the drivers the proper way, they do create a config and i already mentioned what should contain; at least those lines. Is true it can be called 50-digimend.conf - depending how you installed the driver. So, you could have in /usr/share/X11/xorg.conf.d/50-huion.conf or /usr/share/X11/xorg.conf.d/50-digimend.conf with this complete config lines:

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

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

Section "InputClass"  
    Identifier "Huion scroll"  
    MatchProduct "HUION"  
    MatchIsPointer "off"  
    MatchIsKeyboard "off"  
    MatchIsTouchpad "off"  
    MatchIsTablet "off"  
    MatchIsTouchscreen "off"  
    MatchDevicePath "/dev/input/event*"  
    Driver "evdev"  
EndSection

If no config is present, then you create it. In some cases you have to install the xf86-input-wacom and that will create the /usr/share/X11/xorg.conf.d/70-wacom.conf - not useful for your case, but a good model to create a config for other tablets, as exemplified above.

Reason why i offered my help in the first place.
Also, depending on some circumstances that i will not start to enumerate here and now, you have to use the id of the tablet in the config. Since your tablet has 256c:006d then the config will look something like this, and will have the Section entries a bit different:

Section "InputClass"
    Identifier "Huion Stylus"
    #MatchProduct "HUION"
    #MatchIsTablet "on"
    MatchDevicePath "/dev/input/event*"
    MatchUSBID "256c:006d"
    Driver "wacom"
EndSection

Section "InputClass"
    Identifier "Huion Buttons"
    #MatchProduct "HUION"
    MatchUSBID "256c:006d"
    MatchIsKeyboard "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

Section "InputClass"
    # Not Working.
    Identifier "Huion Scroll"
    #MatchProduct "HUION"
    MatchUSBID "256c:006d"
    MatchIsPointer "off"
    MatchIsKeyboard "off"
    MatchIsTouchpad "off"  
    # I think MatchIsTouchpad needs to be on.
    MatchIsTablet "off"
    MatchIsTouchscreen "off"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
EndSection

Since this was the case back in 2018, i don’t think you have to use the ID anymore, but once again, it depends.
The first config should work.

If the issue you have is persisting still, then

xsetwacom --set "$tabletstylus" Button 0 0  
xsetwacom --set "$tabletstylus" Button 1 1 
xsetwacom --set "$tabletstylus" Button 2 2   
xsetwacom --set "$tabletstylus" Button 3 3

should default the buttons to work as per xinput action …