Summary: | Last.fm service not shown | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Thierry Göckel <thierry> |
Component: | Internet Services | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dmeltzer.devel, lfranchi, sven |
Priority: | NOR | ||
Version: | 2.1-SVN | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Thierry Göckel
2009-04-21 00:47:42 UTC
The debug output does however show that the plugin is being loaded: amarok: [PluginManager] Trying to load: "amarok_service_lastfm" amarok: [PluginManager] " " PluginManager Service Info: " " --------------------------- " " name : "Last.fm" " " library : "amarok_service_lastfm" " " desktopEntryPath : "amarok_service_lastfm.desktop" " " X-KDE-Amarok-plugintype : "service" " " X-KDE-Amarok-name : "LastFmService" " " X-KDE-Amarok-authors : ("Shane King") " " X-KDE-Amarok-rank : "100" " " X-KDE-Amarok-version : "1" " " X-KDE-Amarok-framework-version: "40" Are the Ampache and Shoutcast Directory plugins working? The machine is online? If it has no network connection the last.fm plugin won't be shown. Yes, the machine is online and the other services (they are also related to being online, aren't they?) work! I found out about last.fm not working when I wanted to listen to some radio streams of theirs, so I just listened to some shoutcast stations, which worked very well. How exactly does amarok check whether it is online or not? I've got a quite non-functional eth2 interface enabled in /etc/network/interfaces.. should I try to disable that one (or the kde-network-manager linked to it)? Commenting out the lines of the dysfunctional interface in said /etc/network/interfaces solved the problem! Still, I think this is weird because a working interface doesn't need to be defined in that file. This has been fixed a few days ago by the following commit: SVN commit 959621 by mitchell: Make Internet services behave consistently -- a proper fix can go in 2.2 if someone cares. |