Version: (using KDE KDE 3.5.7) Installed from: Unspecified OS: Linux The "love" last.fm function works well. The "skip" function doesn't. In fact when I press "skip" it doesn't load next track, which is not good if the track really sucks ;-) the only workaround found is to stop, then play again (it will load a new track) but this isn't very practical... If you think it's last.fm fault, then please, developers, you may contact last.fm asking some support? Maybe they will listen to you and help to fix the bug.
Damn, you're right. I can reproduce the problem with 1.4.6. Looks like last.fm changed the protocol. I'm gonna ask our resident last.fm guru about it.
It's all very mysterious. Sometimes it works, sometimes it doesn't.. Looks like server problems to me. We'll keep investigating.
This hasn't worked here, not even once, since we've moved to 1.4.6!
On 7 Jul 2007 18:02:40 -0000, Laurent Baum <bugreporter@tabr.homedns.org> wrote: > This hasn't worked here, not even once, since we've moved to 1.4.6! That's pure coincidence though. There were no changes in 1.4.6 in that regard.
Just upgraded to 1.4.7 (on Kubuntu Feisty using MySQL 5.0.32) and got the exact same problem - last.fm's "skip" doesn't do anything. I didn't experience this on 1.4.6
This is a server side issue. That it worked for you with 1.4.6 and doesn't work with 1.4.7 is pure coincidence.
Is there a link or URL where we can track the progress of this issue on the last.fm side?
Yeah, status was changed to RESOLVED, but no explanation to what has been resolved. Bad!
Not looking good, guys - server side issue it may be but the "skip" feature works without any problems on last.fm official client - so on Amarok instead of "RESOLVED" it would be fairer to say "FEATURE NOT SUPPORTED ANY MORE"
The last.fm player uses a different protocol. Both protocols are officially supported though.
Stan: now it takes about 20 seconds for a track to be skipped (and new one be played) but at least it wrok. Thanks ;)
*** Bug 153551 has been marked as a duplicate of this bug. ***
I can reproduce the problem mentioned here in Amarok 1.4.8 using KDE 3.5.8 from the Mandriva packages. And skipping doesn't work at all for me. The standalone lastfm-client works perfectly well. Thus, I'm re-opening the bug. I can supply more information for you as I'm a knowledgeable programmer (of C/C++ and other languages).
Updated the parameters for the bug.
Shlomif at iglu.org.il asked me to check how the bug does here. I'm using 1.4.8 using KDE 3.5.8 from the Ubuntu repositories (Kubuntu installed). I haven't checked the standalone lastfm-client on this machine. When I click Skip, I get "Skipping song..." and after about three seconds, I get new song information and Amarok says it's playing song B while I'm still listing to song A. After about twenty seconds, the new song actually starts. The same happens at the end of a song - Amarok says I'm already playing the new song while the current one hasn't even ended yet. It might be handy if Shlomi and I both do a dump of traffic between Amarok and Last.fm. However, I've heard the password is sent over unencrypted, so we might want to filter that one out. After that, we can do a diff over the traffic.
We can't do anything about this in 1.4 It has been fixed in 2.0 as we now use the same code as the official lastfm client. -> Fixed
*** Bug 165002 has been marked as a duplicate of this bug. ***