Bug 495648

Summary: present windows: can't switch to window with keyboard after entering filter text
Product: [Plasma] kwin Reporter: kdebugs
Component: effects-overviewAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 6.1.5   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kdebugs 2024-10-31 16:55:53 UTC
After triggering the "present windows" selector, I see the various windows.

Previously I could start typing, e.g. "konso" for "konsole" and after dynamically filtering the windows according to what I type, when the results came down to a single window I could then hit return and that window would gain focus, be raised, etc.

Now when the filter results are down to a single window, nothing happens when return is pressed.

This behavior is intermittent, however: sometimes the blue border highlights the window and "return" works as expected.

I notice that if I use the left/right arrow keys, it seems as if there are invisible windows being selected (the blue border goes away for a few taps, then comes back on a window, etc.) Nothing happens when the blue border is gone, and it does work when it is present, but it does not work as would be expected.

This behavior is visible with or without filter text being typed in. E.g. just hit the hotkey for present windows, see e.g. 5 windows presented, then left/right arrow key can select most (not all) of these windows, and for a number of left/right taps in a row nothing is selected, then suddenly a window is selected, etc.
Comment 1 kdebugs 2024-10-31 16:59:14 UTC
$ kinfo
Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-9-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4770K CPU @ 3.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Comment 2 Nate Graham 2024-11-01 15:43:17 UTC

*** This bug has been marked as a duplicate of bug 495536 ***