KDE applications need kfmclient to open links, which is not shipped with kdebase/runtime

Mark Kretschmann kretschmann at kde.org
Wed Nov 26 08:52:34 GMT 2008

On Wed, Nov 19, 2008 at 3:01 PM, Armin Berres <trigger at space-based.de> wrote:
> After reading the following Debian bug report [0] Pino Toscano and me
> discovered the following: To be able to open links most KDE applications
> rely on an installed available kfmclient executable [1]. The problem is
> now: kfmclient is shipped with Konqueror. This means: If Konqueror is
> not installed a lot of applications are not able to open links even with
> another configured browser. For KDE user this isn't such a big problem,
> but a Gnome user e.g. doesn't want to install Konqueror just to be able
> to open external links.
> The question is now: How can we solve this problem? I guess in theory
> kfmclient should be a part of kdebase/runtime and not kdebase/apps, but
> I don't know if this is feasible in pratice. I didn't check yet how
> coupled kfmclient and Konqueror are and when distributed -runtime
> and -apps are two different tarballs.
> Anyway this problem really must be addressed somehow soon.

We've been experiencing the same problem in Amarok 2. Got a bug report for it:


Mark Kretschmann
Amarok Developer
www.kde.org - amarok.kde.org

More information about the kde-core-devel mailing list