Version: (using KDE Devel) Installed from: Compiled sources Following a user report on the kde mailinglist http://lists.kde.org/?l=kde&m=108640700517262&w=2 I looked through the code of KAboutDialog and discovered that it uses KApplication::invokeBrowser, while, if IIRC, KMail uses KRun. Studying the code for invokeBrowser it seems that it uses kfmclient to open the given URL. I think invokeBrowser() should use KRun instead of runtime-depend on an executable from kdebase (which is not required to be installed AFAIK) Thanks, Kevin
This is still a problem in trunk...
I think another issue with this from the user's perspective, is that it pretty much prevents users from another desktop from using popular applications (like digikam, well kipi-plugins). If kipi-plugins needs the kfmclient, which is part of the konqueror file manager... then just to install a popular plugin to a photo-management program the user needs to install pretty much the whole of KDE.
Are there any plans to address this report?
A similar issue has recently be disucssed on kde-core-devel http://lists.kde.org/?t=122710352700002&r=1&w=2 KRun cannot be used directly since it is in the KIO library and the invoke method is "below" that. Probably won't be fixed for KDE3.5 but as far as I understand the discussion there are a couple of options and somebody does have look at them
Fixed in r896218 (will be in kde-4.2). Now invokeBrowser uses kfmclient or xdg-open or kde-open (in a KDE session), and xdg-open or kfmclient or kde-open (out of a KDE session), where "or" means "or, if that is not available".