Bug 250582

Summary: Krunner needs you to press ENTER twice to execute or open what you typed
Product: [Plasma] krunner Reporter: Micael Capitão <micael.capitao>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: chanika, kde-bugzilla
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description Micael Capitão 2010-09-08 17:46:24 UTC 
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

The problem happens since I installed the KDE 4.5 and the 4.5.1 update didn't solve the problem.
Everytime I want krunner to run something, I need to press ENTER twice in order to execute the action. For example, I just need to type "chr" to krunner show the chromium in the list. Then in kde 4.4 series, I just needed to type ENTER once to open chromium, but in kde 4.5 I have always to press ENTER to twice to open it. It happens with everything I try to open or execute via krunner.


Reproducible: Always

Steps to Reproduce:
Bring up Krunner. Type something to krunner open or execute, press ENTER once. Krunner won't do anything unless you press ENTER again.

Actual Results:  
Krunner do what it should (open or execute what I typed).

Expected Results:  
Open or execute what I typed with a single ENTER press.
Comment 1 Aaron J. Seigo 2010-09-13 00:12:06 UTC 
SVN commit 1174602 by aseigo:

if we delay the query, but then we aren't actually running the query, and we have a delayed run in the pipe, try it again
BUG:250582


 M  +12 -0     interface.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1174602
Comment 2 Aaron J. Seigo 2010-09-13 00:14:53 UTC 
SVN commit 1174604 by aseigo:

if we delay the query, but then we aren't actually running the query, and we have a delayed run in the pipe, try it again
BUG:250582


 M  +5 -0      interface.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1174604
Comment 3 Daniel Hahler 2010-09-15 15:03:07 UTC 
*** Bug 243388 has been marked as a duplicate of this bug. ***