I know that "Focus Follows Mouse" is highly disparaged, but it allows me a substantially more efficient work flow than having to click windows every few seconds, so I use it. This is *NOT* "Focus Under Mouse". Anyway, my _guess_ is that with "Focus Follows Mouse" the menu and the run command search window detect that focus is not present and they go away. Despite the fact they never had time to get focus. These windows need to wait until focus has been received before considering going away and then they need to wait at least focus-delay-fraction-of-a-second before allowing a lack of focus to trigger exiting. This is happening almost every time (but not every time). Reproducible: Always Steps to Reproduce: 1. Set focus policy to Focus Follows Mouse 2. Set focus stealing to extreme 3. login a few times and try to use the start menu or the "run command" popup. Actual Results: windows flash on screen and go away Expected Results: windows would wait for focus before they disappear
I do not think it is related to focus stealing. I am now on click-to-focus (as much as I hate it) and it still happens. I can use the run command window by pre-positioning the cursor to where I know the window will pop up, so it _seems_ like some focus following strategy, but I _am_ using click focusing. The run command window stayed up while my mouse meandered from window to window and it did not disappear until I finally clicked one of the windows. The start menu, however, is still inaccessible.
Created attachment 97926 [details] .config/kwinrc
(In reply to bkorb from comment #1) > I do not think it is related to focus stealing. It is. You have set "Focus Stealing Prevention" to "high": FocusStealingPreventionLevel=3 And this causes the problem. Lower it (to "medium" or "low") and there should be no more problems. That's unrelated to the focus "policy", i.e. "click to focus"/"focus follows mouse". *** This bug has been marked as a duplicate of bug 352647 ***