Comment 59 for bug 692462

> Creating a new application shortcut from Chrome still classifies the application as Chrome
> when it is first created, I have to quit Chrome after creating it and then relaunch the app for it to show up.

I guess that this is more or less a race: probably chromium creates the new application window too early, when bamfdaemon has not matched the newly created .desktop file yet.
Maybe reducing the filesystem monitor timeout would fix it, but I'd prefer not to do that not to make bamfdaemon to be too aggressive...