XP-PEN Artist 12 Tablet Issues on KDE Neon (Wayland) – Click Not Registering in Certain Apps

Help
, , ,
1

Hello,
I’m experiencing an issue with my XP-PEN Artist 12 tablet on KDE Neon (Wayland). The stylus is detected and works in some applications, but it does not register clicks in others, especially in Electron-based applications like Vesktop (Discord client), Brave/Chrome (exemple: for Figma).

System Information:

  • Operating System: KDE Neon 6.2
  • KDE Plasma Version: 6.3.0
  • KDE Frameworks Version: 6.10.0
  • Qt Version: 6.8.2
  • Kernel Version: 6.8.0-49-generic (64-bit)
  • Graphics Platform: Wayland

Problem Description:

  • The stylus is detected and moves the cursor system-wide.
  • Clicking works in some applications (Dolphin, KDE system settings), but does nothing in others (Brave, Chrome/Figma, Vesktop).
  • In affected applications:
    • The cursor moves but does not trigger hover effects.
    • Clicking (tapping or pressing the stylus buttons) does not work.
    • Using a mouse instead immediately restores normal behavior (hover and clicks work).
  • libinput debug-events does not capture click events from the stylus, but the stylus is still able to open the on-screen keyboard when tapping inside a text field.
  • evtest captures movement but does not register click events.
  • journalctl -f | grep -i "input" does not show permission errors, but logs related to Maliit (the virtual keyboard) appear when clicking with the stylus.

Troubleshooting Attempted:

  • Permissions & Device Recognition:

    • Added the user to the input group:
      sudo usermod -aG input $USER
    • Checked udevadm info /dev/input/event* to confirm the tablet is detected.
    • Ran libinput list-devices: The tablet is listed but lacks some tablet-specific capabilities.

  • Forcing libinput recognition:

    • Created /etc/udev/rules.d/99-xppen.rules with the following content:
      ACTION=="add|change", KERNEL=="event*", ATTRS{idVendor}=="28bd", ATTRS{idProduct}=="0051", ENV{LIBINPUT_IGNORE_DEVICE}="0"
    • Reloaded rules:
      sudo udevadm control --reload-rules && sudo udevadm trigger
    • No change.

  • Attempted libinput configuration override:

    • Created /etc/libinput/local-overrides.quirks with the following content:
      [XP-PEN Fix]
MatchVendor=28bd
MatchProduct=0051
AttrEventCodeEnable=BTN_STYLUS BTN_TOOL_PEN
    • No effect.

  • Setting environment variables to improve input handling:

    • Added the following to ~/.profile:
      export GTK_IM_MODULE=xim
export QT_IM_MODULE=xim
export XMODIFIERS=@im=none
export WLR_NO_HARDWARE_CURSORS=1
export CHROME_ENABLE_WAYLAND=1
    • Reloaded with source ~/.profile.
    • No change.

I would appreciate any insights or suggestions on how to resolve this issue.

Thanks in advance for your help.

2

It actually works fine in Firefox, so it definitely seems to be an issue with Electron/Chromium-based apps… Any idea how to fix the issue? Btw, disabling Wayland support on Chrome/Brave (running them without the arguments for it) fixes the issue, so it must be related to Wayland…

3

I think I have the same problem
Problem Description: (same as OP)
Chrome/Thorium is not aware that my cursor is hovering over it or that I’m clicking on it with my tablet, and sometimes after focusing Chrome window with tablet, my tablet can’t interact with anything until I click on the new window with another input device (ex: mouse)

The problem appeared after I updated my system this Saturday (along with Plasma 6.3).

System Information:

Operating System: Arch Linux
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.6.72-native_intel-xanmod1-1-lts (64-bit)
Graphics Platform: Wayland

Tablet:
Huion Inspiroy RTS-300

Things I’ve tried so far (that haven’t worked):
Revert wacomtablet to older version
wacomtablet (6.2.5-1 → 6.3.0-1)

Revert to previous kernel patch version
linux-xanmod-lts (6.6.65-1 → 6.6.72-1)

Change chrome flags:
Preferred Ozone platform
Selects the preferred platform backend used on Linux. “Auto” selects Wayland if possible, X11 otherwise. – Linux
#ozone-platform-hint
To X11

I plan on reverting my system to a previous snapshot and upgrading packages one by one.

5

Looks like KWin 6.3 removed pointer emulation for tablets (read blog here), it was for applications that haven’t implemented tablet input in wayland and was removed because it creates a few problems.

So apps like Chrome that haven’t implemented tablet input won’t be intractable with a tablet in wayland.

Possible temporary workarounds:
Running Chrome with KWIN_WAYLAND_EMULATE_TABLET=1
(maybe be removed in the future)

Or running Chrome with X11 instead of native wayland for now.
You probably have the native wayland ozone flag enabled.

For those who come across this, you can help bring this issue to Chromium developers attention and pressing the +1 button just like I did.
https://issues.chromium.org/issues/40282832

3 Likes
6

OMG YES!!! Thank you so much! It works! I hope they fix this issue permanently in the future…
Thanks a lot for your research about it!