FS#9807 - No header info in the .Scrobbler log

Attached to Project: Rockbox
Opened by j-lon (kingsinger) - Friday, 16 January 2009, 20:20 GMT
Last edited by Dominik Riebeling (bluebrother) - Sunday, 05 June 2011, 11:20 GMT
Task Type Bugs
Category Settings
Status Closed
Assigned To No-one
Operating System Sansa e200
Severity Low
Priority Normal
Reported Version Version 3.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I'm using the newest build of RB on a Sansa e250. I just started using Last FM, so I turned on the scrobbler log. When I tried to upload with QTScrobbler, it said it couldn't parse because of missing header info. When I examined the log file in the text editor, after looking at the Scrobbler log spec on the LastFm site, I saw that there was no header info in there.

When I inserted header info manually, Qt Scrobbler could then parse the log file and scrobble the tracks.

I don't know if this is a new bug, or something that has been this way for a while.
This task depends upon

Closed by  Dominik Riebeling (bluebrother)
Sunday, 05 June 2011, 11:20 GMT
Reason for closing:  Out of Date
Additional comments about closing:  no activity since last request for confirmation, which is already a year ago.
Comment by Jonathan Gordon (jdgordon) - Monday, 02 February 2009, 09:35 GMT
what header is qtscrobbler expecting? and where is the actual spec for the log file?
Comment by Jonas Häggqvist (rasher) - Monday, 02 February 2009, 11:06 GMT Comment by Robert Keevil (obo) - Monday, 02 February 2009, 13:51 GMT

If the log file doesn't exist the header is added... is an empty log file being manually created?
Comment by Dave Hooper (stripwax) - Sunday, 18 October 2009, 02:21 GMT
I've seen the scrobbler log file sometimes not having a header, and corrupted first few lines. I wonder if file isn't cleanly closed/flushed on exit in some case. If the file gets corrupted, then a header won't get re-added, of course.
Comment by Bertrik Sikken (bertrik) - Monday, 19 July 2010, 11:11 GMT
Does this still happen?
Can you reliably reproduce it?

Please report rockbox version as the exact number when submitting a bug, "newest build" is completely useless when looking at the bug some time later.