SUMMARY Inactive color palette persists after application is switched to. STEPS TO REPRODUCE 1. Launch two apps 2. Alt-tab between them, making sure that Tab key is released before Alt OBSERVED RESULT Active application uses inactive colors (for headers, checkboxes, highlight, etc) until some keyboard key is pressed. EXPECTED RESULT Active application uses active colors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1
Hi - I can't reproduce the observed result on my Fedora KDE 41 system. Are you able to attach a screen recording (which can be created using Spectacle) of the behavior occurring on your device, to help folks see the specific timing and applications involved? Thanks!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Created attachment 177514 [details] Screen recording There is no need for specific timings, I can reproduce it reliably. In the video I release Alt key a couple of seconds after switching the window, and you can see palette changing. Also I can only reproduce it with "Thumbnail Grid" task switcher. With all other switchers this issue does not occur.
Thanks! Interesting - so I can't reproduce this on either desktop with NVIDIA graphics that I have running, but I *can* reproduce it on my KDE Neon VM. This looks like an exact reoccurrence of https://bugs.kde.org/show_bug.cgi?id=477885 , as it's not just the header palette but also things like the cursor in Konsole not reflecting an active state. What graphics setup (card, drivers, etc.) do you have on the system where this occurs? I'm asking as my Neon VM has no graphics acceleration at all, and that's the first thing that comes to mind that is potentially different and might have something to do with this?
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Seems to be fixed in 6.3