When starting ktorrent 3.2 under kde 4.1 via quicklauncher (alt + f2), you get a message everytime;

Code: Select all

KDEInit could not launch '/usr/bin/ktorrent'.

This happens only with ktorrent.
Known problem?

What happens if you start it in a terminal ?

I've had this problem. Using /usr/lib/kde4/bin/ktorrent as the path should work.

Strange, I installed ktorrent with correct prefix, but still getting this message via krunner.
Also krunner crashed once when launching ktorrent, but it is not 100% reproducible, I wonder if it is related to this

Distribution sidux by any chance?

No, opensuse - I'm mosty running latest revision from trunk (updatet 1x a week)

kriko wrote:When starting ktorrent 3.2 under kde 4.1 via quicklauncher (alt + f2), you get a message everytime;

Code: Select all

KDEInit could not launch '/usr/bin/ktorrent'.

This happens only with ktorrent.
Known problem?

I can confirm the same behaviour with ktorrent 3.1.1 on kde 4.1 on Arch Linux

Have the same on ArchLinux with ktorrent 3.1.2.

I don't see what we can do about this, it's a KDE bug and it is probably caused by the fact that ktorrent forks at startup (like every KDE app which can only have one instance per session)

@George: well, contact kde dev team on #kde-devel and ask them about it. They will probably know what to do.

Today I got this popup:

KLauncher could not be reached via D-Bus. Error when calling start_service_by_desktop_path:
empty

There is still something wrong with this, ktorrent is the only application that gives problems to krunner when starting up.