Bug 345627 - krunner UI is invisible or off-screen when using multiple screens on focus is on "wrong" screen
Summary: krunner UI is invisible or off-screen when using multiple screens on focus is...
Status: RESOLVED DUPLICATE of bug 345628
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Vishesh Handa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-28 21:09 UTC by Bardur Arantsson
Modified: 2015-03-28 22:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bardur Arantsson 2015-03-28 21:09:04 UTC
Hi there,

It seems that somehow krunner gets confused about screen geometry (or something like that) and thus becomes invisible on one of my (physical) screens.

When I activate krunner (via shortcut) while the focus is one a window on my "left" screen, it shows up as expected. When I shift focus to my "right" screen, focus shifts away from the currently focused application, I can type commands and have them executed by krunner.  However I cannot actually *see* the krunner UI anywhere. (I've attached a screenshot of the "kscreen" config.)

After experiencing this the first time, I did try to mess about with some krunner files in .config, but that was *after* things went wrong. (To no avail, hence this bug report.)

FWIW, I'm running what Arch Linux claims is 5.8.0-1. (I'm assuming that the version list on this bugzilla just hasn't been updated yet. If that's not the case, please let me know what you need to pin down a real version number.)

Please let me know if there's any additional information that I can supply that would help!

Reproducible: Always
Comment 1 Bardur Arantsson 2015-03-28 22:11:21 UTC
Sorry, inadvertently made a duplicate because of the ridiculous amount of Bugzilla slowness. The other bug actually has a screnshot.

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