https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #29 from Robin Bankhead <kde.b...@headbank.co.uk> --- Now on plasma-6.2.2 and have noticed some change in behaviour. 1. Triggering has returned to on first manual keypress within the VNC client session, rather than immediately on client connect. 2. On killing and relaunching kglobalacceld, it is fully functional (for both built-in and user-defined shortcuts) and the other input-related corruptions mentioned in OP do not occur. This effectively brings the behaviour back to its state circa plasma-5. Let me therefore bring in two further details from back then that were moot until now: 1. After relaunch, further (manual) keyboard input does not re-trigger the bug in any way that I've found so far. 2. The bug *can* be manually re-triggered using xdotool, e.g. "xdotool type helloworld". (Again, kill and relaunch of kglobalacceld recovers fully.) >From the discussion above, it sounds as though this may be more TigerVNC's bug to fix, but I am doubtful they will be very receptive to a non-systemd-user. If you have any thoughts on whether/how this can be pitched as an issue they should address irrespective of init system, I'd be grateful to hear them. The current easing of the symptoms means it can be worked-around and I can return to Plasma as my VNC daily-driver, but I'd still like to see this resolved once and for all. -- You are receiving this mail because: You are watching all bug changes.
