There appear to be two issues related typing quickly into the kickoff on plasma5: When typing an unambiguous keyword into kickoff and pressing enter quickly, it will sometimes not execute the correct command, but inconsistently execute any one of the intermediate search results it has come up with. For instance if I type "shutdown" and press enter very quickly, it might run "sh" instead, if it didn't manage to come up with the "shutdown" option in time. Similarly, if I type "chromium" and press enter, it might instead open some random image named "chrome.png" from my home folder instead. This appears to happen even on a pretty high-end system with an i7 CPU, 16 gigs of ram and SSD harddrives when typing at a normal 120-130 wpm. This apparently inconsistent behaviour makes it very hard to use the kickoff as a reliable mechanism to carry out tasks. In my opinion, typing something and pressing enter should cause the kickoff widget to delay the execution of the command until it has "finalized" the list, and then pick the first one, in order to achieve consistent behaviour. This would also align it better to the kind of behaviour a user might expect from a shell; typing the same thing several times always results in the same action being carried out. I think this is how it works on windows 8.x and OSX as well, where typing quickly seems to consistently result in the same action; although I have not researched the behaviour very thoroughly on those platforms. Secondly, when typing something into the kickoff very quickly, sometimes the kickoff simply doesn't find any corresponding action at all. This one appears to be much much rarer on fast systems, but happens very frequently (25% of the time) on my netbook with an old intel atom processor. For instance I might type "chromium", and the kickoff will simply come up with no results. Removing a letter or two will kick it back into gear, and it will come up with the normal suggestions for "chromium"; the "Chromium" application, the currently open chromium window, "Run Chromium", and a bunch of files from my home-directory that have "chromium" in the name. Reproducible: Sometimes
*** This bug has been marked as a duplicate of bug 340494 ***