Am 23.01.2018 um 23:27 schrieb Rex Dieter:
Rex Dieter wrote:
> Reindl Harald wrote:
>> when i call something like "cachegrind.out.corecms_cached" from
>> Konqueror all is fine, doing the same roma folderview on the desktop it
>> opens fine *but after* you close kcachegrind you get a error message
>> like in the attachment saying "KDEinit could not start
>> why is there any difference at all and how in the world comes the
>> desktop to the crazy idea that it was not able to open something you
>> just closed after you are done?
> Usually means there's a (minor) bug in the .desktop file used to launch
> the app in question.
> Which version of kcachegrind are you using/testing here?
I can reproduce this testing version 17.12.1 from updates-testing... in my
experience, it means one or both of these keys in .desktop are incorrect:
after launching kcachegrind, I don't see it listening on dbus at all, so I'd
suspect one possible fix would be removing those keys
i don't get the dbus stuff for a simple application at all
why is there so many useless cruft growing on Linux desktops?