SUMMARY When I open multiple windows of the same application, it is really buggy to focus the window you want to work in. Due to the nature of my work, I only had this issue with JetBrains applications (multiple IDEs, version as before as updating to Plasma 6.x). With multiple windows open, at some point (after a not fixed time - kinda randomly), I can't just click into the window, because it would focus the window or application behind that window. STEPS TO REPRODUCE sorry, still trying to figure it out. Kinda just open multiple windows of one application and play around with it? OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux X11 6.7.9-zen1-1-zen (64-bit) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I couldn't find a reported bug or solution for this one for multiple days now. I could imagine that this is duplicated.
If I remove all windows in the background, it works again. Also, closing and reopening the window does help to get it working again.
I can confirm same issue with RubyMine, JetBrains application. KDE Neon, KDE 6.0.2. I also don't know how to reproduce error. It just happens. The problem did not exist before 6.0. by TheR
I forgot to mention that this is not problem isolated to Wayland. It happens under X11 too. by TheR
I'm facing same issue while using Jetbrains application and also couldn't figure out what causes this issue. I'm not quite sure but it may not only happen on Jetbrains application because i have dual monitor setup and uses quite a lot of programs while working with Jetbrains but sometimes it happens on web browser or any other application but i'm running Jetbrains all the time so it is caused by Jetbrains but not sure.
Is this maybe related to this bug report? https://bugs.kde.org/show_bug.cgi?id=483162
(In reply to Stefan Burnicki from comment #5) > Is this maybe related to this bug report? > https://bugs.kde.org/show_bug.cgi?id=483162 Yeah, i think both of these bugs are talking the same issue.
*** This bug has been marked as a duplicate of bug 478556 ***