| Summary: | Window focus and alt-tab are broken with Activities | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | armoire.mountable405 |
| Component: | activities | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | kde-bugs, mullein, nate, plasma-bugs-null, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.8 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
armoire.mountable405
2023-05-03 14:14:53 UTC
Same issue. Changing focus through Alt+Tab or task list does not bring the selected Window to front. launcher are also effected and opens behind other windows as soon as there is at least one window on another activity. But: Input focus for mouse and keyboard is on the correct window! I've been seeing similar behavior for a long time. Oddly, Alt+tab kind of focus on the correct window, but mouse focus selects the previous window. This is the sole reason I don't use Activities, as it really renders them unusuable. Also, once the broken behavior is triggered, if I go into Settings > Window Behavior > Focus, and change the window activation policy to something else and apply it, window focusing starts working correctly (until I activate/deactivate Activities again, at least). Operating System: Gentoo Linux (2.14) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.6.13 (64-bit) Graphics Platform: Xorg and Wayland Do you have the "slide back" effect enabled? ๐๐งน โ ๏ธ 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! So, I was able to fix this behavior in my case by removing a kde file, but unfortunately I'm not exactly sure which file it was. I think it was removing the ~/.config/kdeglobals file, but of course I could be mistaken. However, removing some configuration file fixed the issue in my case. I wish I had more information, or that I had the forethought at the time to save the old version of that file for comparison. ๐๐งน โ ๏ธ 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! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |