I have just upgraded my system (ran emerge -uDv world in gentoo) and since I upgraded all of that (~700 packages) I decided to also upgrade amarok.  I have the svn checked out so I just went and did and svn up + friends.  I started to have issues with amarok responding right off the bat.  It seems that when ever I try to do anything where it needs the cover art it just hangs.  I did not have this issue before the upgrade.  For instance when I am browsing through my collection it halts when I try to expand an album since it wants to display the album in the collection tree.  It also hangs when I want to add a song to the playlist, show the OSD, and so forth.  As I stated I am running svn trunk and am aware that sometimes bugs pop in but I would hate to attribute this to a svn bug and not a problem on my end.  I do now know what diagnostic information to provide.  Please send me some suggestions as to what I can provied.  It should also be noted that I ran amarok as root and loaded up a collection and had the same problem as my regular user.  Thanks in advance.

Justace

Ok...

    So, I did some thinking and figured I could post some extra information to help with the debugging....

    gcc-4.1.1
    binutils-2.17
    kde-3.5.5
    beryl svn + friends
    wm: aquamarine (want to run emerald)

    When I compiled amarok after the svn up I used...

    ./configure --prefix=`kde-config --prefix` --without-debug

    I realize that the without debug does not really get me that far.  What I can do upon request is recompile it and then rerun and save the output.  The messages did not look that usefull to me at the time  but to an experienced person they might be meaningful.  I am also using the xine output plugin..  I can not think of anything else that would be prudent...  Ohh wait...  when amarok is unresponsive the cpu usage goes to 100% and I beleive it has two running threads.

Justace

So, here is some more information.  it looks like the majority of the waits are in the collectiondb file in my home directory.  I found this out by performing an strace (several times) and performing actions that look for the cover art.  I am attaching the output from the recompiled amarok with the debug re-enabled.  Possibly one of you guys can spot a problem.

Yeah, we also got a bug report about this. But the weird thing is that none of use developers can reproduce it. So we'll have to dig a bit deeper.

Please rebuild with --enable-debug=full, and attach the full debug output to this bug report:

http://bugs.kde.org/show_bug.cgi?id=138913 

ok dokie....  I have made some debug outputs + gdb bt's and posted it as an attachement to the bug you listed above.

Justace