Bug 243388 - KDE 4.5: krunner only runs command when waiting for ~2 seconds
Summary: KDE 4.5: krunner only runs command when waiting for ~2 seconds
Status: RESOLVED DUPLICATE of bug 250582
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 249817 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-07-01 22:03 UTC by Daniel Hahler
Modified: 2010-09-15 15:03 UTC (History)
2 users (show)

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 Daniel Hahler 2010-07-01 22:03:02 UTC
Version:           unspecified (using Devel) 
OS:                Linux

When running a command from path (or .desktop file), krunner requires ~2 seconds to recognize the input.

When not waiting a few seconds before pressing Enter to execute the program, the KRunner dialog is just closed, and the program not being started.

Reproducible: Didn't try

Steps to Reproduce:
1. Alt-F2
2. "eclipse", Enter

Actual Results:  
Nothing happens.

Expected Results:  
Eclipse should get started.

Using the whole path directly, e.g. /usr/local/bin/eclipse works without any required pause.

KDE 4.5rc1
Comment 1 Sterling Christensen 2010-09-12 07:04:44 UTC
Same here, except that it just ignores the enter key for about 2 seconds (the dialog doesn't close on the first enter).

Steps to reproduce:
1. start krunner
2. type the 3 letters: "kwr", then hit enter
3. notice that krunner was fast enough to list kwrite in the autocomplete list *before* you could hit enter, so it's not like you're typing too fast for it
4. nothing happens, kwrite doesn't launch, the krunner dialog is still there
5. get annoyed, hit enter a second time
6. now finally the dialog disappears and kwrite launches

This is not a keyboard problem - it is perfectly reproducible (always happens every time) and didn't happen with 4.0-4.4.

KDE 4.5.1 on Gentoo ~amd64
Comment 2 Daniel Hahler 2010-09-12 13:46:18 UTC
I can confirm the steps to reproduce this.
However, the time KRunner is up already gets added to the "minimum 2 seconds" timeout; i.e. if you start KRunner, then wait for 2 seconds "kwr+Enter" will start KWrite properly.
Comment 3 Sterling Christensen 2010-09-13 23:29:56 UTC
Could this be related to bug #249817 ?
Comment 4 Daniel Hahler 2010-09-14 20:15:55 UTC
*** Bug 249817 has been marked as a duplicate of this bug. ***
Comment 5 Daniel Hahler 2010-09-15 15:03:07 UTC
This appears to have been fixed in Kubuntu Maverick, by applying the patch from bug 250582.
I am marking it as duplicate therefore.

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