https://bugs.kde.org/show_bug.cgi?id=523053
--- Comment #3 from [email protected] --- To clarify my setup: I don't have icons directly on a full-screen desktop containment — I have Folder View **widgets** positioned in the corners of each screen (icons in the upper-left of each screen, plus a separate `/data1/tmp` Folder View widget in the lower-right of the right screen). Given your note that KRunner-via-typing only works on the desktop itself and not inside a Folder View widget, I initially wondered if this was just normal focus behavior (focus moving into the widget on click). I retested precisely to check: 1. Fresh boot, fully loaded: typing does nothing at all (presumably no focus yet — expected). 2. Click blank desktop space (outside any widget): typing now correctly opens KRunner. 3. Single-click inside a Folder View widget (on the widget itself, not even an icon): typing stops opening KRunner. 4. Click blank desktop space again: typing still does **not** open KRunner — instead, Folder View type-ahead activates, even on blank space, even though I'm no longer interacting with the widget at all. Step 4 is the key result: if this were normal focus-ownership (typing belongs to whatever you last clicked), returning focus to blank space in step 4 should have restored KRunner, the same as step 2. It didn't. This tells me the desktop containment itself gets stuck in type-ahead mode after any interaction with a Folder View widget, persisting even once you click away from that widget — and only clears on reboot. That's not "focus is legitimately elsewhere," it's the desktop containment's own state getting corrupted by a widget interaction. Separately: even setting root cause aside, this layout (Folder View widgets rather than a full-screen desktop containment) worked correctly on Fedora 43. There's no setting I've found to restore the old typing-to-KRunner behavior on 44/6.7.1 given this layout, which seems worth tracking as a regression regardless of what the underlying mechanism turns out to be. -- You are receiving this mail because: You are watching all bug changes.
