Bug 226009 - krunner should (at least be allowed to) cover yakuake
Summary: krunner should (at least be allowed to) cover yakuake
Status: RESOLVED DUPLICATE of bug 243135
Alias: None
Product: krunner
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-09 09:52 UTC by Rufus
Modified: 2010-06-30 17:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rufus 2010-02-09 09:52:23 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Hi there!
Quite often I find myself having yakuake open to do some root stuff. If now I want to quickly start some program as my regular user, I fire up krunner. I do not open a new yakuake tab, since I don't want to block it with a running process and neither do I want to care about appending a '&' to the command to set yakuake free again.
However, in this use case I press <Alt><F2>, and nothing seems to happen, since krunner is covered by yakuake and doesn't accept keyboard input. Since this might be a matter of personal preference I'm asking for at least an option to have krunner appear on top of yakuake.

Best wishes,
Rufus
Comment 1 Anselmo L. S. Melo (anselmolsm) 2010-02-27 03:44:49 UTC
I can't reproduce, here running:

Qt: 4.6.3 (kde-qt)
KDE trunk KDE 4.5 >= 20100224

That's strage, it's exactly my daily use case of krunner & yakuake for work.

Can you see krunner "hidden" behind yakuake (using transparency, maybe) or is it a supposition? Thanks =)
Comment 2 Anselmo L. S. Melo (anselmolsm) 2010-06-30 17:07:31 UTC
Oh, ok, I see, this issue happens with 'keep window above other windows;' active.
Comment 3 Anselmo L. S. Melo (anselmolsm) 2010-06-30 17:19:14 UTC
According to bug 243135, this issue was fixed on KDE SC 4.4 but is back on 4.5.0 RC1 - a regression.
Based on this fact, this report will be merged with the newer one. Thanks.

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