Created attachment 177999 [details] KWin tabbox sticky current index SUMMARY When all windows are minimized, pressing Escape while Alt+Tab'ing through a tabbox dismisses it but does not reset current index position. Next time Alt+Tab is pressed and Alt is held, the current position in the tabbox advances from the previously "current" but not activated window/app. Seems to only be the case when all windows/apps are minimized so the desktop is active/focused. STEPS TO REPRODUCE 0. Set your Alt+Tab behavior to cycle through apps (not sure this is required compared to cycle through all windows of all apps, but we certainly need something other than "all windows of the current app" here). Regarding virtual desktops, my tabboxes only show windows/apps from the current virtual desktop. 1. Open multiple windows of different apps. 2. Minimize all windows. 3. Press Alt+Tab, release Tab while holding Alt down, to keep the tabbox open without actively cycling it. 4. Press Escape. 5. Repeat step 3. OBSERVED RESULT Each time at step 3 the next window/app gets highlighted in the tabbox, marking it current (without activating because you press Escape next). EXPECTED RESULT Current item position should be reset after closing the tabbox. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.10-arch1-1 (64-bit) Graphics Platform: X11
Hi - I can't reproduce on my Fedora KDE 41 device by following those steps. Are you able to check on your system if that issue reproduces under a Wayland session?
🐛🧹 ⚠️ 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!
I don't know why did you have to bring up Wayland, but… the issue seems to be fixed in Plasma 6.3.3 (maybe earlier). Not sure which commit fixed it, not involved enough to dig.