https://bugs.kde.org/show_bug.cgi?id=520043
Bug ID: 520043
Summary: USI 2.0 stylus presses stop working a couple seconds
after first proximity_in event
Classification: Plasma
Product: kwin
Version First unspecified
Reported In:
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
On the Framework laptop 12 with the stylus in USI 2.0 mode, a couple seconds
after the pen first comes within proximity of the screen when Kwin is started
with SDDM and automatic login configured with kde system settings, the pen
presses stop working (can't use the pen to "click" on anything like a mouse),
but hovering still moves the cursor. Switching the pen to MPP 2.0 mode in the
bios fixes this, but then battery state-of-charge reporting fails.
STEPS TO REPRODUCE
1. start KDE with SDDM and automatic login
2. use stylus for a couple of seconds
OBSERVED RESULT
Pen presses stop working
EXPECTED RESULT
Pen presses should emulate a left click on a mouse
SOFTWARE/OS VERSIONS
Operating System: KDE Neon 24.04
KDE Plasma Version: 6.6.4
KDE Frameworks Version: 6.25.0
Qt Version: 6.10.2
ADDITIONAL INFORMATION
Running "sudo journalctl -f -b" and then using the stylus before it stops
working prints a whole bunch of
"2026-05-11T11:09:41.333810-05:00 an-framework12 konsole[2366]: Can't send
tablet event with no proximity surface, ignoring"
where konsole is the current application that has focus, then the messages stop
and stylus presses stop working
Running "systemctl soft-reboot" or "kwin_wayland --replace" seems to fix this,
but the latter throws some crash reports.
Although KWin stops forwarding stylus presses, libinput still recognizes them.
Possibly related: https://bugs.kde.org/show_bug.cgi?id=512549
This may not even be a bug with KDE, but with either Xwayland or wayland's
tablet protocol.
--
You are receiving this mail because:
You are watching all bug changes.
