I\'m having some problems with getting amarok to subscribe to audioscrobbler. It has worked before, but a couple of days ago i got a \"failed to submit...\" in amarok for every song. First I thought it was related to the latest problems audioscrobbler have had, but when I tried the scrobbler-plugin for XMMS, using the same scrobbler-account, it works fine. So the problem most be amarok related somehow.

The only scrobbler error I get from amarok is this line:

amarok: [Scrobbler] [WARNING!] KIO error! errno: 49

And that doesnt say much to me or even Google.

Any ideas will be very helpfull

bump same here

if you got the recent svn version, please try a recompile. as it turned out markey experimented a bit with the code

regards,
muesli

No, I use the 1.2.3 from Gentoo portage. Should the problem appear there?

error persists even with the recent svn version.

Output:

[code:1]
...*snip*...
amarok: [Scrobbler] [WARNING!] KIO error! errno: 49
amarok: [void CollectionDB::createTables(DbConnection*)]
amarok: [KDE::«»ProgressBar::«»ProgressBar(QWidget*, QLabel*)]
...*snip*...
amarok: [virtual KDE::«»ProgressBar::~ProgressBar()]
amarok: [StatusBar] 1hideMainProgressBar()
amarok: [StatusBar] [WARNING!] NOT-IMPLEMENTED: void KDE::«»StatusBar::«»shortLongMessage(const QString&, const QString&«»)
amarok: [Scrobbler] Handshake url: http://post.audioscrobbler.com/?hs=true ... u=alanceil
amarok: [StatusBar] 1resetMainText()
amarok: [Scrobbler] [WARNING!] KIO error! errno: 49
amarok: [void CollectionDB::createTables(DbConnection*)]
amarok: [KDE::«»ProgressBar::«»ProgressBar(QWidget*, QLabel*)]
...*snip*...
[/code:1]

Stats:
Suse 9.2
amaroK SVN
KDE 3.3
taglib 1.3.1
Engine: gstreamer 0.8.10

Post edited by: alanceil, at: 2005/05/13 22:46

i have the same problem too!but if i lounch amarok from shell i don\'t read any audioscrobbler problem. but unfortunately i cannot submit neither to audioscrobbler nor read the tags from musicbrainz! i m very sad.. how can i resolve these problems?

musicbrainz works (for me) ... (screenshot: http://tom-f.org/pics/screens/mbrai.png )

scrobbler does still refuse to work...

[edit]just updated again, and tada~... it worked, thanks B)[/edit]

Post edited by: alanceil, at: 2005/05/14 21:53

yep, thats true.
error 49, i use svn version /update every day/ and i cant figure out that problem since month or sth like dat. i dont know what is that 49 error. i search by google and nothing.
cheers

\"amarok: [Scrobbler] [WARNING!] KIO error! errno: 49\"

Now I cant find any logical explanation for when it works and when it doesn\'t.

A few minutes ago I got af succesfull submit of a dozen old tracks en queue from submit.xml, and then a few minutes later when amarok tried to submit the next dozen tracks from submit.xml, then the KIO error came again.

KIO error code 49 means server timeout:

ERR_SERVER_TIMEOUT = 49

Some other typical errors when amaroK is trying to contact Audioscrobbler are:

ERR_COULD_NOT_CONNECT = 23
ERR_CONNECTION_BROKEN = 24

All of the KIO error codes are defined here:

http://developer.kde.org/documentation/library/3.4-api/kio/html/global_8h-source.html#l00166

Audioscrobbler is just too slow to handle the large amount of submissions at the moment. Let\'s hope that they will get their systems in better shape. In the meantime of course we could make the amaroK error messages a bit more clear.

There are many, many and once more many threads about these submission problems on Audioscrobbler forums, here is just one of them:

http://www.audioscrobbler.com/forum/28/_/32104

This problem is still present for me even though Audioscrobbler is now up and running again. Submission works fine from bmp/xmms, but not from amarok. I\'m using the svn version from May 21st, with the gstreamer engine. I compiled the source with enable-debug=full, but I get no debug output from amarokapp (never have!) so I can\'t provide that I\'m afraid. Other possibly relevant information: Fedora Core 3; sometimes behind proxy, sometimes not (usually works fine either way); 12000+ songs in my AS profile.

I\'d be grateful if anyone has any more ideas on this, because I love scrobbling, and I\'d hate to go back to xmms!

thanks,

--
Nick

Kick!

Anyone got any ideas on this?

Or even just how to get debug info from amarok! (see above post for details)

--
Nick

Somewhere in a bug report one user pointed out a problem with our scrobbler code. IIRC the interval in which the right time for submission is checked is too short, so it can jump over it in some cases.

Unfortunately I can\'t remember what report that is, so the patch is kinda lost. Perhaps you can find it, it must be something with scrobbler in the title.

However, if this bug exists, it would result in amaroK not trying to submit at all. If you see something like \"Failed to submit..\", then that can\'t be it.

markey wrote:

Somewhere in a bug report one user pointed out a problem with our scrobbler code. IIRC the interval in which the right time for submission is checked is too short, so it can jump over it in some cases.

Unfortunately I can\'t remember what report that is, so the patch is kinda lost. Perhaps you can find it, it must be something with scrobbler in the title.

However, if this bug exists, it would result in amaroK not trying to submit at all. If you see something like "Failed to submit..", then that can\'t be it.

I don\'t see "Failed to submit", so this sounds like a possible cause. I\'ll search the bug db and see what I can find.

Thanks for the pointer