[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE applications need kfmclient to open links,
From:       "Mark Kretschmann" <kretschmann () kde ! org>
Date:       2008-11-26 8:52:34
Message-ID: e93871060811260052j691dfa9ewbccaf08c4bfbfe90 () mail ! gmail ! com
[Download RAW message or body]

On Wed, Nov 19, 2008 at 3:01 PM, Armin Berres <trigger@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:

http://bugs.kde.org/show_bug.cgi?id=171995

-- 
Mark Kretschmann
Amarok Developer
www.kde.org - amarok.kde.org
[prev in list] [next in list] [prev in thread] [next in thread]