Amarok's bug reporting reports error'kfmclient'

Bug #120006 reported by Gerhard Klünger
6
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: amarok

Ubuntu 7.04 german version, all updates installed.

Trying to report abug with menu "Help > report bug" displays errmsg:

"Could not Lauch Browser
Could not launch the vrowser: Could not find service 'kfmclient'.
OK"

Gruß, Gerhard

Revision history for this message
Harald Sitter (apachelogger) wrote :

The Amarok package doesn't depend on Konqueror, which is the package that holds kfmclient, which would be used as default client to start a webbrowser for KDE applications.

Please set:
Settings -> Configure Amarok... -> [x] Use another browser:
to --- xdg-open --- and try whether this fixes the issue.

Changed in amarok:
assignee: nobody → apachelogger
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Gerhard Klünger (g-kluenger) wrote :

I installed Amorka 1.4.7, went to settings ... and keyed in "xdg-open", clicked "apply and went to Help > report a bug >Launch Bug report wizzard and err msg "could not find service 'kfmclient' was displayed.

In case I misunderstood what to key in the alternate browser field please set in your answer the required string enclosed in double quotes. I use the default firefox webbrowser. The meaning of "--- xdg-open ---" is not clear for me what is meant with the "---" at the beginning and end of the string "xdg-open". BTW: I also tried the string "xdg -open" with a blank between xdg and the minus sign.

Gruß, Gerhard

Changed in amarok:
status: Incomplete → Confirmed
Revision history for this message
Luke Schlather (luke2760) wrote :

Yeah, I suspect this is hard coded.

Revision history for this message
Luke Schlather (luke2760) wrote :

I should be more descriptive than that. Entering xdg-open into the alternative browser does nothing, so I suspect they've hard coded this into the bug reporter. Maybe someone should enter this in upstream with amarok? It seems like this would affect any installation where Amarok is installed independently of KDE.

Changed in amarok:
assignee: apachelogger → nobody
Revision history for this message
Francisco Borges (francisco-borges) wrote :

For the record; the problem still happens in Intrepid with Amarok 1.4.10

Revision history for this message
Mitch Golden (mgolden) wrote :

This issue afflicts all KDE 3.5 applications, and includes not just Konqueror (which is what kfmclient is opening) but also khelpcenter, and possibly others.

The issue appears to be that there are separate directories /usr/share/applications/kde and /usr/share/applications/kde4, and the
desktop files construct separate sycoca files. Since kfmclient.desktop is only installed in the kde4 directory, the KDE 3.5 apps can't find it in their sycoca.

A simple fix is just to make a symlink from the kde4 file into the kde directory. I.e:

cd /usr/share/applications/kde
sudo ln -S ../kde4/kfmclient* .
kbuildsycoca

and the problem disappears.

I will be filing a bug and a patch against Konqueror for this.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Should be fixed now with Amarok 2 in Jaunty (packages are also available for Intrepid, see kubuntu.org) since Amarok 2 is a KDE4 app. Amarok 2 also uses the standard KDE4 bug reporting dialog.

Changed in amarok:
status: Confirmed → Fix Released
Revision history for this message
gnappy (gnappy-deactivatedaccount) wrote :

Still appearing in Amarok 2.0.1 under KDE 4.1.3. "kfmclient not found." I use Ubuntu 8.10.

Revision history for this message
gnappy (gnappy-deactivatedaccount) wrote :

Changed The status to "Incomplete" because I still experience this bug with amarok2.

Changed in amarok:
status: Fix Released → Incomplete
Revision history for this message
Mitch Golden (mgolden) wrote :

Regarding the bug in the KDE3 version, please see the bug
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/328919

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still a problem with Amarok 2.2 in Kubuntu 9.10?

Changed in amarok (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Changed in amarok (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.