Amarok had been woring fine until last week when I downloaded some new music directly into my normal music directory (I don't know if this was the cause, but, just in case).
Anyway, now whenever I try to "rescan collection" or when it tries to on startup, it hangs at 99% for about 5 minutes, then gives up with an error message like:
"Sorry, the Collection Scan was aborted, since too many problems were encountered.
Advice: A common source for this problem is a broken 'TagLib' package on your computer. Replacing this package may help fixing the issue.
The following files caused problems:" and a giant list of some file repeated many many times often with random unreadable characters tacked onto the end.

Here's a screenshot:
[img]http://aycu38.webshots.com/image/45877/2003111104964654032_rs.jpg[/img]

Moving or erasing the files in question just causes it to do the same thing to some other arbitrary file (though I haven't yet tried to move my whole library to see where/if it would end...)

From looking at some the other similar posts, it looks like people had problems with either taglib stuff or running via samba, but my taglib stuff hasn't changed and hasn't failed before, and these files are all stored on a normal XFS partition. How could it be coming up with these crazy file names?

I'm running Debian sid with libtag1c2a 1.4-8+b1 (hasn't changed since 2007-05-08) and amarok 1.4.7-1+b2 (hasn't changed since 2008-01-08).

Any suggestions? Please?

Just updated to amarok 1.4.8 (debian package version 1.4.8-2) and ilbtag1c2a version 1.4-8.1, and still have the same issue.
I also tried moving all my music into another directory, creating a clean database for amarok to start with, and giving it just one lone file with a boring name (hello.mp3). It still managed to come up with a never ending supply of wild non-existant variants as above.
Seriously, does anyone have any idea where amarok could be digging up these crazy file names?

To truly create a clean database, you'll need to make sure you move/backup ~/.kde/share/apps/amarok/collection.db and ~/.kde/share/config/amarokrc (assuming you're using the default sqlite database).
This type of error can sometimes be caused by odd files other than music files that Amarok doesn't always seem to ignore.

dangle_wtf wrote:To truly create a clean database, you'll need to make sure you move/backup ~/.kde/share/apps/amarok/collection.db and ~/.kde/share/config/amarokrc (assuming you're using the default sqlite database).
This type of error can sometimes be caused by odd files other than music files that Amarok doesn't always seem to ignore.

Thanks for the reply. Actually I'm using MySQL as a db backend, so creating a clean database is literally just that.
For experiment's sake I tried creating a new user that's never used amarok before, and used the sqlite database backend on the same single file hello.mp3 directory, and had the same problem (however when using sqlite, the error message was accompanied by a segfault (amarok itself was survived though). I didn't have debug symbols for amarok installed so the backtrace was useless. I'll see if i can recreate the same error with debug symbols installed).