Amarok 1.3.0 is unresponsive for a couple of minutes after it starts. Extremly annoying. Using armrok 1.3.0 from portage using GStreamer with alsaink on gentoo with gentoo-sources. What gives?

does it rescans the collection?

maybe switching to osssink helps :huh:

\" does it rescans the collection?\"

Doesn\'t seem to be doing anything. And if I drag another window over it, then off of it, armarok will show that window until it unfreezes.

\'maybe switching to osssink helps\"

Doesn\'t help.

Upgraded to 1.3.1, and I get the same problem.

Switched to Xine engine, much faster. However, it won\'t play flac files.

I get the same error no matter what engine I use. amarok stand still doing absolutely nothing for a long time. Amarok says it is builing collection, but the harddrive is not working so that\'s just plain out lying

Starting amarok in a konsole, I get the output:

conny@abbey ~ $ amarok
amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don\'t run gdb, valgrind, etc. against this binary! Use amarokapp.
conny@abbey ~ $ QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
Very strange! got a DCOPReplyWait opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyDelayed opcode, but we were not waiting for a reply!
QWidget::setMinimumSize: The smallest allowed size is (0,0)
QComboBox::setCurrentItem: (speakerComboBox) Index 1 out of range