After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 518489 - Only scrobbles manually selected tracks
Only scrobbles manually selected tracks
Status: RESOLVED DUPLICATE of bug 349586
Product: banshee
Classification: Other
Component: Other Extensions
0.13.1
Other All
: Normal normal
: 2.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-24 21:23 UTC by Peter O'Malley
Modified: 2008-02-25 17:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peter O'Malley 2008-02-24 21:23:42 UTC 
Please describe the problem:
Banshee will only audioscrobble tracks that are selected by the user. That is, the first song of an album will get scrobbled because it was selected (i.e. double-clicked), but the subsequent songs that come up automatically (in sequence) don't get scrobbled.

Steps to reproduce:
1. Start a song playing.
2. Wait for it to finish and another one to automatically come up.
3. Go to last.fm user page and notice that only the first song was scrobbled.


Actual results:
Banshee plays the music as expected but only one song gets scrobbled.

Expected results:
All the songs that got played should be scrobbled.

Does this happen every time?
Yes.

Other information:
Ubuntu Feisty x64, repository version of Banshee. After much googling this is all I came up with: http://ubuntuforums.org/showthread.php?t=679014 (unanswered post describing same problem)
Comment 1 Peter O'Malley 2008-02-24 22:36:34 UTC 
OK, I spoke a little too soon. Closing and reopening banshee seemed to fix it. So I can't reproduce the bug anymore, and it seems to be quite a trivial bug now.
Comment 2 Andrew Conkling 2008-02-25 17:50:12 UTC 
Hm, I recall this bug in Feisty: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/62637. Seems like it was fixed.

As per the comments there (my own, actually ;), this is actually bug #349586, so I'm marking this one as a duplicate. If you encounter the problem again just let me know. And, of course, feel free to report any further bugs you find. :)

*** This bug has been marked as a duplicate of 349586 ***