This is incredibly frustrating.

There is no music on this machine.  I'm basically using it as a jukebox which pulls music from DAAP shares (mt-daapd, aka Firefly Media Server) all over the house.  Amarok is apparently the only music player that can create a playlist out of songs from different DAAP shares and then save that playlist, so it's really my only option.

Here's the problem.  Every one out of about 15 times you drag a file from a DAAP share to the playlist, X appears to freeze in a very strange way: Amarok's status display says "Populating Playlist" and sticks like that, but everything keeps moving (such as the timer, the mini-visualization in the bottom of the window).  However, no application on the machine will respond to the mouse or keyboard.  I can Ctrl-Alt-Backspace (which restarts X and makes me have to start everything all over again and rebuild the playlist) or Ctrl-Alt-F2 and kill Amarok from the command line, but that's it.

What the heck is going on here?

can you track down whether it's any particular track, album, server or some pattern? Might help narrow down the problem.
Also, try running Amarok in a console, and check for errors or debug info.

dangle_wtf wrote:can you track down whether it's any particular track, album, server or some pattern? Might help narrow down the problem.
Also, try running Amarok in a console, and check for errors or debug info.

There is no pattern I've been able to discern so far.  It is not consistent between tracks, albums, or servers.

Okay, every time I add a track, it does this:

QDom: saving invalid character , the document will not be well-formed
QDom: saving invalid character , the document will not be well-formed
QDom: saving invalid character , the document will not be well-formed
QDom: saving invalid character , the document will not be well-formed
amarok: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol 'daap'.
amarok:

But that's when it works.  I've added about 10 tracks so far and it hasn't broken... okay!  I just got it to break!  And precisely the same message was produced.

::bump::

Help?