Well it doesn\'t really hang but it starts to work on the disk and the GUI is unresponsible (no redraws) for appox. one minute.

I guess the collection is rescanned at every start!? How can I suppress this behavior? The \'Watch folders for changes\' option in the collection part of the config dialog is not checked.

It\'s really annoying and makes the program nearly unusable for me.

any relevant output when you start amarok from the command line?

No, it \"talks\" about starting the application, loading the engine etc. and then this \"hang\" occurs. Last line says:

[code:1]amarok: [StatusBar] 1hideMainProgressBar()[/code:1]

So rescanning the collection is just a guess. If I rescan from within the app there is plenty of debug output in the konsole.

Maybe it\'s the same problem that I\'ve got.
In the console does it repeat the message \"GStreamer-WARNING **: pushing data on non-negotiated pad dvddemux0:current_audio, not allowed.
\" several times?
Don\'t know what I can do to stop it!
Thanks

No there\'s no output while it \"hangs\". If the HD activity stops I can use the program without further problems. But this really long delay + bad response times of other apps caused by the massive disk IO is a real show stopper for me.

I\'ve updated to 1.3.5 and now the problem is gone.