Comment 7 for bug 572432

Revision history for this message
Horrendus (stefan-derkits-net) wrote :

Workaround that worked for me:

-) Scanned my Collection via amarokcollectionscanner and this Description:
http://amarok.kde.org/wiki/Batch_Mode
-) When it crashed (with above Error), I checked the File
amarokcollectionscanner_batchfullscan.log and moved the File it should have
read next outside of my Collection
-) Started the Scan again, it crashed again, but much later
-) Repeated the second Step and then started the scan again :)

This way I found out which Files crashed the collectionscanner and moved them out of my Collection.
Another tip: If you have your Collection on a NFS Share or so ... scan it directly on your Server, is much faster, especially it doesn't really hang for that long when it gets to a File where it crashes.