GNOME Bugzilla – Bug 573297
Last.FM Radio Stations fail to play tracks.
Last modified: 2009-03-04 19:09:46 UTC
I noticed this issue on the night of the 25th Feb 2009. Banshee is able to log in and select some recommended tracks to play. However, pressing play results in an X to the left of the track name. The error on the console last night was something along the lines of: "500 Internal Server Error" I cannot replicate that message, but it still shows the following: "banshee --debug" ------------------------------------------------------- [Debug 18:15:24.079] Successfully tuned Last.fm to lastfm://group/Banshee [Debug 18:15:25.057] Adding 5 Tracks to Last.fm Station lastfm://group/Banshee [Debug 18:15:27.709] Player state change: Idle -> Loading [Debug 18:15:27.917] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [Debug 18:15:27.918] Player state change: Loading -> Idle [Error 18:15:27.921] GStreamer resource error: OpenRead [Debug 18:15:28.179] Player state change: Idle -> Loading [Debug 18:15:28.293] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [Debug 18:15:28.293] Player state change: Loading -> Idle [Error 18:15:28.295] GStreamer resource error: OpenRead [Debug 18:15:28.550] Player state change: Idle -> Loading [Debug 18:15:28.734] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL [Debug 18:15:28.734] Player state change: Loading -> Idle [Error 18:15:28.735] GStreamer resource error: OpenRead [Debug 18:15:28.987] Player state change: Idle -> Loading [Debug 18:15:29.118] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL ---------------------------------------------------- I was concerned that this behaviour was limited to Banshee, so I returned to Rhythmbox (which was working until the 25th also). It also puts an X next to the track name. However, clicking it gives the following error message: ""http://kingpin6.last.fm/user/c3fb83bef1d6b1d65331d6daa554c17c.mp3": Invalid ticket" I have tried Rhythmbox on two Ubuntu desktops, with two different last.fm accounts. Both throw a similar error. I only have Banshee on one PC, so I can't test it twice. ----------------- To make sure that it's not just my last.fm account or my IP address that is frowned upon, I downloaded the official Last.FM client for linux. It works perfectly. No problems there. In it's log, I see it searching for tracks with the following URLs: "http://195.24.233.49:80/last.mp3?Session=c5d06de02199a74dd5969e9e6f6bfcb1" That is quite different from the 'kingpin9' URLs Rhythmbox(and I assume, Banshee) seem to be searching for. Only one person has reported a similar problem in this timeframe: http://www.last.fm/group/Banshee/forum/26658/_/508195 Oh, and someone complained of this in the IRC room #banshee too. Could it be a problem on my end, or is it a Last.FM API change? My location is England, incase that is a factor.
I have the exact same behaviour. Switching to the latest gstreamer stuff doesn't fix the issue either.
The same/an equal problem with rhythmbox: Gnome Bug 573302 I can only play the first track in banshee 1.4.2 when I stared gnome with openSuse 11.1 and could not play any tracks of a last.fm playlist in my old banshee 1.4.0. This problem with lastfm seem to me not only a problem of banshee. The same/an equal problem is reported with rhythmbox: Gnome Bug 573302 Bug 573302 – lastfm protocol changed: set version to 1.5 when requesting playlists. 2009-02-26 19:07 UTC http://bugzilla.gnome.org/show_bug.cgi?id=573302 There seems to be a patch for rhythmbox. greetings Martin
That's good to know. It is certainly beginning to look like a result of something Last.FM has done. I tried again today and the behaviour you describe is accurate - it occasionally allows me to play the first track in the list, but after that, nothing. I've tried skipping tracks and letting the track end on it's own. Same result - a white X on the next track.
Martin, thanks for finding the Rhythmbox bug. I had the same problem at the time this was reported : I was only able to sometimes play one track from Last.fm, the others were failing. I tried again today (2009-02-28) and it seems to work OK, I've been playing several tracks in a row. Are you guys still experiencing the problem ? Maybe it was a temporary glitch on (some ?) Last.fm servers and the protocol version change was working around it ?
It is now working for me also. I haven't downloaded any updates to Banshee, so whatever was done to fix this was probably on Last.FM's side. I have a feeling that the reasons for this break were somewhat more sinister than a simple mistake. From what I've heard, they are trying to push everyone onto the new API which is rather more restrictive and *may* require payment to use. All idle speculation and unfounded claims though. I'm just glad it works again, for the time being;)