Summary: | run command dialog does not accept the enter key | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | Michal Svoboda <kde> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andresbajotierra, finex |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Bug here |
Description
Michal Svoboda
2009-01-02 14:19:27 UTC
Well, I have experienced such behaviour with recent builds. I will confirm if I can reproduce it one more time with an updated build. Created attachment 29831 [details]
Bug here
after entering "kate" I pressed Enter a lot of times... only when removing a part of the command and entering "kate" again, the Enter command works
Mh, here using: Qt: 4.4.3 + qt-copy-patches-889120 KDE: 4.1.86 (KDE 4.1.86 (KDE 4.2 >= 20081221)) kdelibs svn rev. 904448 / kdebase svn rev. 904448 on ArchLinux x86_64 - Kernel 2.6.27.10 I have experienced this bug This seems to happen when you slowly type the command and when some different icons overlap/ or when two entries appears for a command (the .desktop one, that contains the Program name and icon; and a default one for running the executable (the "gear/service" icon) This may be related to bug 177815 For me, when it happens, then it doesn't matter whether I type slowly or rapidly. Also, the number of icons is irrelevant here; happens for commands that have no .desktop file, as well as for the ones that do. I've tried with only "Applications" or "Command line" runners and the bug is still there. The first time I enter "kate" , Enter key doesn't launch the app (even when the Kate icon/gear is there and selected), deleting some character and re-typing it, enabled the Enter key to launch the app. Here using: Qt: 4.4.3 + qt-copy-patches-889120 KDE: 4.1.87 (KDE 4.1.87 (KDE 4.2 >= 20090101)) kdelibs svn rev. 905636 / kdebase svn rev. 905636 on ArchLinux x86_64 - Kernel 2.6.27.10 *** This bug has been marked as a duplicate of bug 175176 *** |