bcooksley wrote:If you're interested in fixing the issue yourself, the correct place to start looking is the sources for the Applications runner - which all three affected areas (KRunner, Kickoff Search and Homerun) share.

You can browse this at http://quickgit.kde.org/?p=kde-workspac ... 2Fservices
If you would like to download the source to work on it (and possibly submit patches) you can clone the git repository from git://anongit.kde.org/kde-workspace.

I'll have to take a look at it. It seems like it should be simple, since menus update just fine. Homerun can even be configured to display apps available for install, so it should be able to handle the ones that are already installed. I imagine that the current code runs a cron job to update a database, or is triggered by events such as logging in. Since a database already exists, it seems pointless for the runner to create its own. But I'm not that familiar with how these things work in KDE.

The database the runner uses is hopefully the same one all other KDE applications use - the Sycoca. It is updated on a number of events, which includes logging in. No cronjob is used to the best of my knowledge.

What I would suspect is caching interfering, or searches not matching due to case sensitivity or the application being mistakenly seen as hidden.

I have the same problem on KDE 4.13.2: Changes in .desktop files are only reflected in KRunner search results upon re-login, not even kbuildsycoca4 --noincremental works. They still show up in the menu though. Anyone know if a bug was ever filed for this? I can't find one right now, but krunner has so many open bugs I might have missed it.

Just wondering, if you relaunch KRunner by running the following, does it "fix" the issue?

Code: Select all

kquitapp krunner
krunner &

bcooksley wrote:Just wondering, if you relaunch KRunner by running the following, does it "fix" the issue?

Code: Select all

kquitapp krunner
krunner &

It worked for me.

Okay, this is due to a caching issue in KRunner. Please file a bug report against the applications runner at bugs.kde.org.

It looks like I've been affected by this bug as well. Like was suggested, killing and restarting krunner fixes the problem in the Alt-F2 menu, but does nothing for the kickoff launcher. Logging in and logging out solves the problem, though. Perhaps this is a bug in more than just krunner?

I couldn't find the bug report that was mentioned above. Should I file a new one?

I could not find an existing issue for this, so I made a new one:

https://bugs.kde.org/show_bug.cgi?id=341693