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

Kevin Krammer kevin.krammer at gmx.at
Wed Nov 19 18:31:29 GMT 2008

On Wednesday 19 November 2008, Armin Berres wrote:
> Heyya!
> 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.

Could probably be changed to use kioclient.

Some parts of the functionality kfmclient had in KDE3 were moved to the new 
kioclient since they weren't Konqueror specific.


Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20081119/2a13f284/attachment.sig>

More information about the kde-core-devel mailing list