Cursor jumps around randomly clicking everything when connecting a graphics tablet

YoungFellow · 15 March 2022 05:24

Hello there.
I connected my brand new graphics tablet. And the first time I used it it worked fine.
I had installed xsetwacom and digimend-kernel-drivers-dkms, as per @bogdancovaciu’s instructions.
It worked fine at first, but then the next day I pluged it in and out, and in again, and then the cursor started jumping around madly and started clicking everything.
After some reading there should be some .conf files relating to the tab in /usr/share/X11/xorg.conf.d/, but there are none. There might have been before though.
I tried to make one following this post, but that didn’t work either.
I really hope to resolve this issue, if there is anything else you want me to post then please let me know. But I will not be able to post any outputs when the tab is plugged in, because the mad cursor makes the laptop unusable.
PS: The first time I plugged it in, I gave it the correct name (HUION H950P), but after that it started giving it this name: HID 256c:006d
PS 2: This is what I put in my custom config file in /usr/share/X11/xorg.conf.d/:

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

Thanks.

bogdancovaciu · 15 March 2022 05:32

If by disconnecting and connecting again, or turning off and on again the tablet you do not get a proper functionality of the tablet stylus, then make sure you are not on wayland session. If you switch to X11 session and still the same issue after disconnecting and reconnecting the tablet, then there might be something else we should look at.

Also, in case you want to use it with multiple applications, not just drawing applications, and the “click” is not working with the Stylus, add this line to your ~/.bash_profile

export QT_XCB_TABLET_LEGACY_COORDINATES=1

Note:
I see you shared this:

YoungFellow:

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

Only one Section "InputClass" in that file please … and you can’t use two drivers … has to be Driver "wacom" and NOT Driver "evdev"

YoungFellow · 15 March 2022 06:16

Firstly, thanks @bogdancovaciu for kindly answering.

I’m sure that I’m not using wayland. because I have a login script that uses xrandr, and it’s working fine (the xrandr script)

I followed your instructions and made this file: /usr/share/X11/xorg.conf.d/70-wacom.conf (this is the same name it was given before)
Contents:

Section "InputClass"
    Identifier "Huion Stylus" 
    MatchProduct "HUION" # I commented this line out and uncommented and got the same result
    MatchIsTablet "on" # I commented this line out and uncommented and got the same result
    MatchDevicePath "/dev/input/event*"
    MatchUSBID "256c:006d"
    Driver "wacom"
EndSection

Now the cursor is not moving around madly, but it still sakes about lightly, then when I move the pen further away from the tab it starts to shake even more until the pen is too far away from the tab. And the name is still wrong.

bogdancovaciu · 15 March 2022 06:26

Never seen that … but
You have to make sure what file you edited … especially if you followed this

check 70-wacom.conf and 50-digimend.conf
For your case, the 70-wacom.conf should remain as is and you should edit the 50-digimend.conf - but in some cases there is a different file name …

YoungFellow · 15 March 2022 07:27

I noticed this other weird thing , it only happens when using the tab’s styles:

ezgif-4-703cc48c7b

(That’s latte-dock, in case you’re wondering)

I tried both of them, and they both gave the same result.

But while searching my history in my terminal I found this:

Screenshot_20220315_122236

So these were the file names, and I remember now that I removed these files hoping that they’ll reset and sort them selves out, but that obviously didn’t work.

bogdancovaciu · 15 March 2022 07:36

So you deleted the files … well, reinstall the packages and start over with the edit …

Interested more in defaults … because i do not know if that is an issue with latte-dock or something else, and since with my tablet i can’t reproduce it, not sure where to look.

YoungFellow · 15 March 2022 07:39

So I reinstall xsetwacom and digimend-kernel-drivers-dkms right?
Anything else to reinstall?
EDIT: what’s the package name for xsetwacom? yay does not recognise it as xsetwacom.
EDIT2: found it (xf86-input-wacom)

YoungFellow · 15 March 2022 08:00

Reinstalled, and got this beautiful notification :

Screenshot_20220315_124953

Okay, the the cursor does not jitter at all now.

I realised this problem is with all of plasma, and the clicks don’t work with some software and others work fine.

ezgif-4-67750241a1

YoungFellow · 15 March 2022 08:12

I found this:

Also:

ezgif-4-8a86dd2864

YoungFellow · 15 March 2022 08:21

Contents of new 70-wacom.conf:

# Some of the below input classes appear 3x times, once for each of
# "tablet", "touchscreen", and "touchpad" to ensure that the Wacom
# driver is not accidentally bound to other types of hardware that
# Wacom has made which are not handled by the wacom driver (e.g the
# Wacom Bluetooth Keyboard)
#
# https://sourceforge.net/p/linuxwacom/bugs/294/

Section "InputClass"
        Identifier "Wacom USB tablet class"
        MatchUSBID "056a:*"
        MatchDevicePath "/dev/input/event*"
        MatchIsTablet "true"
        Driver "wacom"
EndSection

Section "InputClass"
        Identifier "Wacom USB touchscreen class"
        MatchUSBID "056a:*"
        MatchDevicePath "/dev/input/event*"
        MatchIsTouchscreen "true"
        Driver "wacom"
EndSection

Section "InputClass"
        Identifier "Wacom USB touchpad class"
        MatchUSBID "056a:*"
        MatchDevicePath "/dev/input/event*"
        MatchIsTouchpad "true"
        Driver "wacom"
EndSection

Section "InputClass"
	Identifier "Wacom tablet class"
	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
	MatchDevicePath "/dev/input/event*"
	MatchIsTablet "true"
	Driver "wacom"
EndSection

Section "InputClass"
	Identifier "Wacom touchscreen class"
	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
	MatchDevicePath "/dev/input/event*"
	MatchIsTouchscreen "true"
	Driver "wacom"
EndSection

Section "InputClass"
	Identifier "Wacom touchpad class"
	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
	MatchDevicePath "/dev/input/event*"
	MatchIsTouchpad "true"
	Driver "wacom"
EndSection

# Serial Wacom devices should always be one of tablet, touchscreen, or
# touchpad so we can safely get away with just one match section in
# these cases
Section "InputClass"
        Identifier "Wacom PnP device class"
        MatchPnPID "WACf*|WCOM*|WACM*|FUJ02e5|FUJ02e7|FUJ02e9"
        MatchDevicePath "/dev/input/event*"
        Driver "wacom"
EndSection

Section "InputClass"
	Identifier "Wacom serial class"
	MatchProduct "Serial Wacom Tablet"
	Driver "wacom"
EndSection

Section "InputClass"
        Identifier "Wacom serial class identifiers"
        MatchProduct "WACf|FUJ02e5|FUJ02e7|FUJ02e9"
        Driver "wacom"
EndSection

# Hanwang tablets
Section "InputClass"
	Identifier "Hanwang class"
	MatchProduct "Hanwang"
	MatchDevicePath "/dev/input/event*"
	Driver "wacom"
EndSection

# Waltop tablets
Section "InputClass"
	Identifier "Waltop class"
	MatchProduct "WALTOP"
	MatchIsTablet "on"
	MatchDevicePath "/dev/input/event*"
	Driver "wacom"
EndSection

# N-Trig Duosense Electromagnetic Digitizer
Section "InputClass"
	Identifier "Wacom N-Trig class"
	MatchProduct "HID 1b96:0001|N-Trig Pen|N-Trig DuoSense"
	MatchDevicePath "/dev/input/event*"
	Driver "wacom"
	Option "Button2" "3"
EndSection

# Dell Canvas 27 (touch part is an Advanced Silicon, pen part a Wacom)
Section "InputClass"
        Identifier "Dell Canvas 27 Touch"
        MatchUSBID "2575:0204"
        MatchDevicePath "/dev/input/event*"
        MatchIsTouchscreen "true"
        Driver "wacom"
EndSection

# Surface Go
Section "InputClass"
        Identifier "SurfaceGo Touch"
        MatchProduct "ELAN9038:00 04F3:261A"
        MatchDevicePath "/dev/input/event*"
        Driver "wacom"
EndSection

# Nuvision Solo 10 Draw (Supports Surface Pens)
Section "InputClass"
        Identifier "Nuvision Solo 10 Draw"
        MatchProduct "04F3200A:00 04F3:22F7"
        MatchDevicePath "/dev/input/event*"
        Driver "wacom"
EndSection

bogdancovaciu · 15 March 2022 09:06

Well, the 70-wacom.conf looks fine, but the other file is important for you i guess, but if works … now you just have to try to calibrate the Tablet in the Settings in the Tablet tab

Also, if you have dual screen, is possible that is mapped to both simultaneously, hence the cursor is off somehow.

This is how i have mine:

Play with the settings there.

YoungFellow · 15 March 2022 10:03

Yep, I got that to work. Thanks

YoungFellow · 15 March 2022 11:09

Just to let anyone reading this know, when I suspend the laptop (put it to sleep) with the tab plugged in. I get this () problem. So you have to plug it out before suspending, and then plug it in after waking it up.

system · 18 March 2022 01:10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.