I have a 3-monitor setup, with the left-most screen being the primary. Some times I get krunner in a very strange state as follows... When I invoke the krunner with Alt+Space (or "Run command" from desktop context menu) when the mouse is in the left-most screen, then krunner opens correctly (screenshot 1) in the left-most screen top middle position. If the mouse is in any other screen and I invoke krunner, then krunner opens on the primary left-most screen in the top left corner. Now krunner is not visible, it is a transparent window (screenshot 2). I can interact with it from the keyboard and, for example, type "urxvt" and press <Enter> and get an urxvt window open. Although now krunner window won't close and I won't be able to type "urxvt" and get a new urxwt window open. If I switch to another desktop when this krunner is open I can see a part of the window that was underneath the krunner when it opened in place of where krunner is open (screenshot 3). I can still type "krunner" and press <Enter> and get an urxvt window open at this point. When krunner is in normal state, I can close it by either clicking the "x" button, or pressing <Alt>+<Space> on the keyboard. I have "focus follows mouse" setting and I can also close krunner by hovering my mouse over some window that gets focus and krunner goes away. If I have the krunner open in this confused state, I cannot get it to close -- it doesn't take mouse input and a click where the "x" button would otherwise be drawn does nothing. If the mouse is not in the primary display, pressing <Alt>+<Space> doesn't close krunner, but instead tries to open it again. I can tell that since I see the window-with-old-content (let's call it a phantom window) animating as it would be sliding in when krunner is opening. Focusing on windows does not close the phantom either. At this point one way to close that window is to place the mouse in the screen of the primary display and press <Alt>+<Space>. That will close the phantom window and open a proper and fully-functional krunner window. Another way to close the phantom window is to kill krunner. Reproducible: Sometimes Steps to Reproduce: The behavior is not reproducible always, but only sometimes. If I kill krunner and start it again, then krunner seems to work properly. I suffer from other multi-monitor problems as well (namely https://bugs.kde.org/show_bug.cgi?id=353722) and most of the time I need to restart plasmashell when attaching extra monitors and enabling them with xrandr. It _seems_ that krunner gets in its confused state after such manipulations. xorg-server 1.18.1-3 xf86-video-intel 1:2.99.917+579+g74cd4d0-1 (Intel HD 4400 card)
Created attachment 98043 [details] Screenshot 1
Created attachment 98044 [details] Screenshot 2
Created attachment 98045 [details] Screenshot 3
This looks like it is related to bug 344328, which has the same basic issue but lacks the details about the phantom window visible when switching to another desktop.
I've just tested and I can't replicate this issue. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!