I upgraded from Amarok 1.1 to 1.2 the other day, and since that day, Audioscrobbler has had new signups disabled. Bad luck!

I\'ve never used Audioscrobbler before, so I don\'t have a login for it.

As a result, Amarok 1.2 is crippled! It can scan my collection, but upon reaching 99%, it pops up the \"Configure Amarok\" window and moves automatically to the Scrobbler tag.

Whether I leave username and password blank, or fill them in with random characters, clicking OK does not allow the media scan to finish.

Even if I untick \"Submit the tracks I play\", the problem persists!

I don\'t know if this is relevant, but every time the Scrobbler tag pops up (which it does, every 30 seconds or so), the console from which I ran amarok echoes the following:

[toby@tobyjr toby]$ QObject::connect: No such signal KTextEdit::changed(const QString&)
QObject::connect: (sender name: \'kcfg_OsdText\')
QObject::connect: (receiver name: \'osdpreview\')
QWidget::setMinimumSize: The smallest allowed size is (0,0)

Anyway, the net result of all this is that my media collection appears empty (being unscannable) so I am unable to play any music with Amarok.

Can anyone suggest a way to get around this?

Hello,

I am using 1.2.3 and also don\'t have a scrobbler ID. I don\'t have this problem though. My collection scanned fine.

Thanks! I\'d gone for 1.2.0 (The most recent rpm available for Mandrake), but seeing your message mention 1.2.3 inspired me to have another go at compiling the latest version from source. 4 hours later, and Amarok works perfectly (Albeit without GStreamer ). So thanks for the hint.

Well, there are newer versions of amaroK for Mandrake in our download section (perhaps not for your version of Mandrake).

It is frustrating when packagers decide they don\'t need to bother with minor point releases... it means users get stuck with a buggy version (1.2.0 was only out 2 weeks before 1.2.1, btw).

Post edited by: eean, at: 2005/05/10 09:59