I've just installed AmaroK 1.1 on Slackware 10. I installed gstreamer as well to avoid startup errors. When I try to build a collection amarok crashes. Besides not being able to load a collection everything else is working great. But without a working collection, amarok is not the best player available to me. If the collection would work I think amarok would be my choice.

This won't solve the problem, but open a terminal, type amarok, and let it start. Then try building a collection, and post the error message from the terminal screen, which at least will say what's going on. I've been having problems with the compiling of sqlite - see posting elsewhere.

I have been getting similar problems when trying to build a collection - the following error is in console.

TagLib: TagLib::ID3v2::Header::parse() - One of the size bytes in the id3v2 header was greater than the allowed 128.
TagLib: Encrypted frames are currently not supported.
TagLib: Encrypted frames are currently not supported.
TagLib: Encrypted frames are currently not supported.
KCrash: Application 'amarok' crashing...
amarok: Fatal IO error: client killed

I have been getting similar problems when trying to build a collection - the following error is in console.

TagLib: TagLib::ID3v2::Header::parse() - One of the size bytes in the id3v2 header was greater than the allowed 128.
TagLib: Encrypted frames are currently not supported.
TagLib: Encrypted frames are currently not supported.
TagLib: Encrypted frames are currently not supported.
KCrash: Application 'amarok' crashing...
amarok: Fatal IO error: client killed

Those crashes while scanning the Collection are caused by TagLib, which we use for reading tags. In TagLib 1.3 support was added for additional formats like m4a and aac, and it turns out that this is pretty unstable.

What you must do is locate these files and remove them before scanning. Ideally, you would report any file that causes a crash to the TagLib bug database at http://bugs.kde.org, so the problems can be fixed.

amaroK 1.1.1 will contain a logging function that will write each processed path into a logfile, so you can easily see which file caused the crash, and report this file.

@markey
I have amaroK 1.1.1 now - where can I find the logfile?
If taglib 1.3 is the reason for the scanning problem - why is taglib 1.3 mandatory to compile amaroK 1.1.1 (why not to use taglib 1.2, I don't need the new buggy features of taglib)? Without the collection function amaroK is not better for me than any other mp3-player under linux.

Marco

OK - I could circumvent the taglib problem: compiling amaroK with having taglib 1.3 installed and after that downgrade taglib to 1.2. It is not really the best way but at least it works...
Before (or after) scanning the collection one should define the tag filter - otherwise nothing will be displayed after scan and you think it's a bug again...

Ciao

Marco