Bug 397066

Summary: KRunner doesn't respect active screen state
Product: [Plasma] krunner Reporter: greywolf813
Component: generalAssignee: Kai Uwe Broulik <kde>
Status: REPORTED ---    
Severity: minor CC: mgraesslin, nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=427069
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description greywolf813 2018-08-01 18:48:01 UTC 
When activating KRunner with a keyboard shortcut, it will always appear on the screen the mouse is on, regardless of mouse focus setting or current active screen. This situation makes it impossible to use a keyboard shortcut to change screens and then execute a command with krunner without moving the mouse. That sort of defeats the purpose of keyboard shortcuts.

Steps:

Use a keyboard shortcut to change active screen, with or without "seperate screen focus" enabled, without "focus follows mouse" enabled. Activate KRunner with Alt+F2.


Actual Results:

KRunner opens on whichever screen the mouse is on, and any commands run from it open on said screen.

Expected Behavior:

KRunner, and a command run with it, execute on the current active screen, regardless of mouse position.


Platform:

OpenSUSE Tumbleweed, KRunner 5.48.0
Comment 1 Kai Uwe Broulik 2018-08-02 07:20:13 UTC 
Martin, is there a way to query that from KWin or how does that work? (Right now KRunner indeed just checks mouse position and matches it to a QScreen)
Comment 2 Martin Flöser 2018-08-02 19:49:51 UTC 
No, KWin does not expose internal data to other processes.
Comment 3 greywolf813 2018-08-05 01:15:53 UTC 
Is skipping that mouse location query and letting KWin choose the screen an option?