After I type in an application and it is selected in krunner, usually pressing enter will launch the application. Since I upgraded to KDE 4.9.3 this function has stopped working. I have to manually click the program for the application to be launched. Reproducible: Always Steps to Reproduce: 1. ALT-F2 to start Krunner 2. Type any application. 3. When the application is selected, press ENTER Actual Results: Nothing happens when I perform the steps above. Expected Results: When I press ENTER after typing the application name in krunner. The application should be launched.
Using Krunner (Alt+F2) Expected: Type partial name of application (ex: 'konso', 'system sett', etc.), have desired application show up as first in krunner list (ex: 'konsole' when typing partial 'konso'), hit return/enter, should launch Konsole (first in suggested list). Actual: No reaction. Expected: Type entire name of application (ex: 'konsole'), shows 'konsole' it suggested list, enter/return should launch 'konsole'. Actual: No reaction. After running Krunner (alt-F2), and typing: "konso".. if you press the up arrow (which goes through command history), then press down arrow, focus returns as was expected initially Running Kubuntu 12.10.
Regression caused by 1b878ffb Aaron, is this intended?
*** This bug has been confirmed by popular vote. ***
I can confirm this bug on Gentoo Linux (x64). Phil's workaround works for me too, but I would rather have Krunner accept the first suggestion right away when I press Enter.
Git commit 110504efad0116480df8ab17ab4d66a8fee1f905 by Aaron Seigo. Committed on 15/11/2012 at 14:20. Pushed by aseigo into branch 'KDE/4.9'. Revert "dont accidentally trigger the last match" This reverts commit 1b878ffb55e6e1b7d51559ab8170c219768fa58b. works as expected in master (nee 4.10); not sure why it does not in 4.9 and i don't have the time to suss it out. it can remain broken the way it was prior to this commit in 4.9. M +2 -5 krunner/interfaces/default/interface.cpp http://commits.kde.org/kde-workspace/110504efad0116480df8ab17ab4d66a8fee1f905
*** Bug 310259 has been marked as a duplicate of this bug. ***
I have this issue with KDE 4.9.3 (archlinux x86_64). Great to know it has been fixed. Thanks.
I'm seeing similar symptoms as this bug (return) after upgrading to kde-4.9.90 (4.10 beta2) :(
I can confirm that I don't have this issue in KDE 4.9.4 anymore.
So this issue is back with KDE 4.10?
Not really back. The suspected problematic commit was *only* reverted for KDE/4.9 branch. It is still contained in KDE 4.10 betas.
So this needs to be reopened.
Why was the patch/fix merged only in the 4.9 branch? Why not merge it to master/HEAD or whatever the development branch is, so that the patch/fix gets merged in future releases as well?
Because the developer who fixed it thought 4.10 was not affected, see comment #5.
Please merge it into the latest 4.10 and further development branches. So that this issue never comes back again. Thanks.
(In reply to comment #16) > Please merge it into the latest 4.10 and further development branches. So > that this issue never comes back again. > > Thanks. *Please merge it into later branches as well.
Present in 4.10 beta2
Still present in latest trunk.. please fix this as it makes krunner pretty much useless for fast program execution..
still present in 4.10 RC2......
Asking for he same patch that went to 4.9 branch to be included in 4.10 https://git.reviewboard.kde.org/r/108197/
Interestingly, the problem disappeared for me somewhere along the line, definitely working on now on 4.9.97. One think I did was clear my plasma caches in /var/tmp/kdecache-<user>/*.kcache
Here the problem still exists even when clearing the cache. Rex it should have worked all along in the 4.10 series but I don't understand why it would work for you and not for others. Anybody else willing to try clearing the cache and see if it fixes it for them?
My experience implies this problem is mostly reproduciable under the following condition: 1. Create a brand new account and log in 2. in krunner, type "konqueror" exactly and slowly, wait for all matching to appear and stabilize, press "Enter"
(In reply to comment #23) > Here the problem still exists even when clearing the cache. Rex it should > have worked all along in the 4.10 series but I don't understand why it would > work for you and not for others. > > Anybody else willing to try clearing the cache and see if it fixes it for > them? I just cleared my cache of all the *.kcache files and it fixed it for me temporarily. The problem returned after I logged out and logged back in again. Running Fedora 18, 4.9.97
*** Bug 312698 has been marked as a duplicate of this bug. ***
(In reply to comment #25) > (In reply to comment #23) > > Here the problem still exists even when clearing the cache. Rex it should > > have worked all along in the 4.10 series but I don't understand why it would > > work for you and not for others. > > > > Anybody else willing to try clearing the cache and see if it fixes it for > > them? > > I just cleared my cache of all the *.kcache files and it fixed it for me > temporarily. The problem returned after I logged out and logged back in > again. Running Fedora 18, 4.9.97 Same here. Removing .kcache fixes this for me temporarly.
Could any one try again with latest master? Seem the problem related with this: https://bugs.kde.org/show_bug.cgi?id=254365 which already fixed in commit 3894923 in KDE/4.10 and master branches of kde-workspace by aseigo.
Tested in latest project Neon packages and the problem is fixed.