GNOME Bugzilla – Bug 675335
Last.fm audioscrobbling hasn't worked since April 30, 2012
Last modified: 2012-05-03 23:26:43 UTC
Created attachment 213336 [details] Banshee log file. None of the tracks I have played have appeared on my last.fm profile since April 30, 2012. Obviously I have been playing tracks since. The log seems to indicate an issue with the date format.
Thanks for the bug report! This is a known issue and there is already a bug open for it: https://bugzilla.gnome.org/show_bug.cgi?id=667499 The issue is somehow related to invalid data surrounding the playtime of your track(s). I am not sure why exactly it is happening yet but I am looking into adding some extra validation to keep it from happening in the future. For right now I would recommend looking in ~/.cache/banshee-1/extensions/lastfm/audioscrobbler-queue.xml. My guess is that you will see all of your played tracks since 4/30 in there. If you see any negative numbers for 'StartTime' then this is probably the issue. For right now your choice is to either go through that file and manually fix the entries or remove the entries/tracks entirely from the XML file. My bet is once you handle the invalid entries in the xml file your scrobbling will work going forward.
(In reply to comment #1) > Thanks for the bug report! This is a known issue and there is already a bug > open for it: https://bugzilla.gnome.org/show_bug.cgi?id=667499 > > The issue is somehow related to invalid data surrounding the playtime of your > track(s). I am not sure why exactly it is happening yet but I am looking into > adding some extra validation to keep it from happening in the future. > > For right now I would recommend looking in > ~/.cache/banshee-1/extensions/lastfm/audioscrobbler-queue.xml. My guess is that > you will see all of your played tracks since 4/30 in there. If you see any > negative numbers for 'StartTime' then this is probably the issue. > > For right now your choice is to either go through that file and manually fix > the entries or remove the entries/tracks entirely from the XML file. My bet is > once you handle the invalid entries in the xml file your scrobbling will work > going forward. Sorry, I didn't see the existing bug, searched for last.fm. The solution above (fixing the negative entries in the cache file) worked for me (so far anyway). There was only one negative entry, and it was also the first entry at the beginning of the file if that is of any consequence. Thanks again.
I'm closing this as a dupe like Phil adviced. Phil: could you report the bug locally if you had James' original file? If yes, James: by any chance did you save it before fixing it? Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 667499 ***
Sorry, I meant "reproduce", not "report".
(In reply to comment #3) > I'm closing this as a dupe like Phil adviced. > > Phil: could you report the bug locally if you had James' original file? If yes, > James: by any chance did you save it before fixing it? > > Thanks for the bug report. This particular bug has already been reported into > our bug tracking system, but please feel free to report any further bugs you > find. > > *** This bug has been marked as a duplicate of bug 667499 *** I already have the xml file from the other bug that I was planning on using for my tests once I have some free time. Any additional examples, though, would be most helpful. James, any chance that you could provide the XML file with the problem entry in it?
Sorry, no I do not have the XML file with the problem entry. I do have a copy of the XML file, but after the starttime was "corrected". The starttime was indeed negative and the value itself was quite a bit larger than the other entries I think around -6000000000. Hope that helps.
It does help, thank you. I have some work ahead of me to test various scenarios and I will make sure to include this one. Thanks again for reporting!