[master] skip/ban/love buttons for last.fm streams don't work

Bug #179556 reported by Daniel Hahler
30
Affects Status Importance Assigned to Milestone
Amarok
Fix Released
Medium
amarok (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: amarok

Reproduce:
1. Add a radio station to the playlist
2. Start playing
3. Add another station after it
4. Press the Amarok "Next Track" button

ACTUAL RESULT:
Amarok switches to the next station in the playlist, indicates that it plays it and says "connecting to stream resource" for a few seconds, but keeps playing the current/previous station!
Only when the currently playing song ends, Amarok starts playing the next station.

EXPECTED RESULT:
Amarok should stop playing the current station and play the next one instead.

This is not the case, if the next item in the tracklist is a "normal" song (e.g. from local media) or another playlist.
Only if the next track is also a lastfm radio station, it keeps playing the current song till the end.

This is with amarok 1.4.8-0ubuntu1 in Ubuntu Hardy.

[appended]

From duplicate bug 230150, there are similar issues with ban and love buttons.

Changed in amarok:
importance: Undecided → Low
status: New → Confirmed
Changed in amarok:
status: Unknown → Confirmed
Changed in amarok:
status: Unknown → Confirmed
Changed in amarok:
status: Confirmed → Fix Released
Revision history for this message
Lydia Pintscher (lydia-pintscher) wrote :

Marking as fix released as the new Last.fm protocol is implemented in Amarok 2 now.
It will not get fixed by upstream for the Amarok 1.4 series as it involves massive code changes which are not going to be introduced in this stable release.

Thank you for your report.

Changed in amarok:
status: Confirmed → Fix Released
Revision history for this message
Mario Limonciello (superm1) wrote :

Since this is only fixed upstream, but still present in Amarok 1.4 (which ships with Ubuntu Hardy), it should be marked as Triaged for now in Ubuntu. This way when future people go to report this problem they'll find an open bug and not think that it should be functional. The bug should get closed when we switch to Amarok 2.

Changed in amarok:
status: Fix Released → Triaged
Andrew Ash (ash211)
description: updated
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed with the release of Amarok2 packages to Jaunty.

Changed in amarok:
status: Triaged → Fix Released
Changed in amarok:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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