Hi,

I've been using amarok for ages now and I absolutely love it, apart from one thing. Every so often my database will become corrupt (I assume this is what is happening) and collection scans will freeze on around 80% and bring amarok to a grinding halt. Furthermore, playing a song will often cause it to grind to a halt doing something for a few minutes before it might come back to life or it might die altogether leading me to have to kill the process. This has happened at least three times now and each time clearing the database and starting from scratch works. This is clearly not satisfactory as I'd quite like not to lose all the info in the db (or it's a bit pointless in the first place!). It's happened across multiple versions (I'm now using 1.4.6 as of yesterday - no change) and also on both SQLlite (or whatever it was called) and mysql (what I use now).

Looking at collection_scan.files and removing the file in there doesn't help (it just get replaced with another file and it still stops around 80%). Furthermore the files mentioned there are often old ones I've had in my collection for ages which never used to cause problems.

All my music is on an ext3 partition, not FAT or NTFS or anything, so that's not the cause.

It seems people have similar problems... from looking at the forum, but is the only solution _really_ just to clear the database? Surely this is unsatisfactory?

Thanks,

Richard Hayden.

All SQLite 3.3 versions have a known bug that can lead to database corruption (see sqlite.org). It's unclear whether Amarok is affected by this bug.

Amarok 1.4.7 is going to ship with SQlite 3.4, which no longer has this particular issue.

Hi,

Thanks for your response, but note that I am using mysql now and the issue I described is still present.

Thanks,

Richard.

Oh, I should have read more closely Anyway, I'm not aware of any issues related to MySQL databases. AFAIK database corruption is very unlikely with MySQL.

Indeed... I would have thought database corruption was unlikely at least corruption due to actions of mysql itself. Any ideas then as to what could be wrong/how I can address this?

Thanks,

Richard.