https://bugs.kde.org/show_bug.cgi?id=347153
--- Comment #42 from Dmitry Batrak <dmitry.bat...@jetbrains.com> --- The problem wasn't reproducible with Plasma 5.18.8 (in Kubuntu 20.04.4), but is reproducible again with Plasma 5.24.4 (in Kubuntu 22.04) and 5.24.5. I believe, it's a regression after https://bugs.kde.org/show_bug.cgi?id=421068. The previous discussion mentions that it could be a problem with client code (Java implementation in particular), but I think that, now at least, this is a KWin issue, affecting 'globally active' (in ICCCM terms) clients in general. As a justification, and as a tool to investigate the issue, I'm attaching source code for a simple native 'globally active' focus client application (see focusTest.c). All it does is changes the window background on receiving and losing focus. To reproduce the issue, focus the test app, then use Alt+Tab to switch to an application in a different virtual desktop (filtering by virtual desktops should be disabled in task switcher settings), then Alt+Tab back. The window won't be focused as expected - with background rendered in white. Judging from xtruss-generated logs, KWin does send WM_TAKE_FOCUS message to the client, and the client, in turn, requests focus on its window using SetInputFocus, but the request isn't satisfied by the X server. This can be due to only one reason - an 'old enough' timestamp passed. As the client just uses the timestamp received in WM_TAKE_FOCUS message, KWin must be sending the stale timestamp in the described case. -- You are receiving this mail because: You are watching all bug changes.
