On my slackware 10.1 system, with amarok 1.3.1, using the xine engine, i will get these errors that pop up occasionally when i change tracks. Launching amarok using the command line it dumps this to the console:

[code:1]
amarok: [CollectionDB] sqlite3_step: BUSY counter: 1
...
amarok: [CollectionDB] sqlite3_step: BUSY counter: 21
amarok: [CollectionDB] [ERROR!] Busy-counter has reached maximum. Aborting this sql statement!
amarok: [CollectionDB] [ERROR!] [virtual int SqliteConnection::insert(const QString&, const QString&«»)] sqlite_step error.
amarok: [CollectionDB] [ERROR!] database is locked
amarok: [CollectionDB] [ERROR!] on insert: INSERT INTO related_artists ( artist, suggestion, changedate ) VALUES ( \'Incubus\', \'The Offspring\', 0 );
[/code:1]

it sill continue this for a while until it will finally finish. These errors also appear when it takes seconds for it to change tracks. Also after these errors appear, my collection seems to disappear and refreshing it does not get the tracks back.

I have the same problem (and same distro)

I also have the same problem, using the same distro and xine but amarok version 1.3.2.
Disabling the option \"Retrieve similar artists\" in last.fm solves that particular problem with the \"related_artists\" table but there appears to exist similar problems with other tables:

[code:1]
amarok: [CollectionDB] [ERROR!] Busy-counter has reached maximum. Aborting this sql statement!
amarok: [CollectionDB] [ERROR!] [virtual int SqliteConnection::insert(const QString&, const QString&«»)] sqlite_step error.
amarok: [CollectionDB] [ERROR!] database is locked
amarok: [CollectionDB] [ERROR!] on insert: INSERT INTO statistics ( url, createdate, accessdate, percentage, playcounter ) VALUES ( \'[....]\', 1128299008, 1128299008,38, 1 );
amarok: [static void PluginManager::unload(amaroK::«»Plugin*)]

[/code:1]

I\'m using the builtin sqlite db.

Sounds like slackware is revealing a known-bug with sqlite and threading (essentially sqlite can\'t thread).