Bug 501992 - Wacom Tablet no longer works in Electron apps and MPV
Summary: Wacom Tablet no longer works in Electron apps and MPV
Status: RESOLVED DUPLICATE of bug 500309
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 6.3.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-25 18:20 UTC by Alexandr Podgorniy
Modified: 2025-03-25 18:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Podgorniy 2025-03-25 18:20:04 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
After update to plasma 6.3 wacom tablet stopped working in wayland apps that ignores tablets by default, like Vesktop (electron based), MPV player. Before that KDE used some workaround that sends fake mouse clicks into apps, and now it's don't. I tried searching the settings, but i can't find option to turn this workaround on.

STEPS TO REPRODUCE
1. Update to plasma 6.3, use wayland session.
2. Download MPV player or Vesktop, or any electron app
3. Try to navigate app using only wacom tablet.

OBSERVED RESULT
wacom tablet completely ignored

EXPECTED RESULT
Mouse-like behavior, like it was in plasma 6.2 and like it is on X11.

SOFTWARE/OS VERSIONS
Windows: no
macOS: no
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: yes
KDE Plasma Version: broke after 6.3 update, now on 6.3.3, still not fixed
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Comment 1 Antonio Rojas 2025-03-25 18:25:56 UTC

*** This bug has been marked as a duplicate of bug 500309 ***