For some reason, every time I bring up Amarok and start playing a song, the little visualization bars right below the playlist (the ones that let you know a song is actually playing), these things will move for about 2 seconds after hitting play, but there will be no sound whatsoever during that time.  Then the bars will stop moving entirely, and if I let it sit for another minute or two, the app grays out and needs to be force-quit.  Every time I force quit the app, a process called "amarokapp" is still lingering around, and I have to kill it in order to reopen Amarok.  But even after reopening Amarok, it will crash again as soon as I start .

Originally, it stopped working because I uninstalled kdelin, and after reinstalling it, Amarok worked fine for a day or so, and then the problem cropped up again the next time I used Amarok.  Once, it started working again after I rebooted, only to have it come back in the same way.

Running Amarok from the shell doesn't produce any weird errors, and I have no clue where the log file is for this app.

Any ideas what could be causing this or what I can look at to figure this out?  This app worked beautifully up until about a week ago.

If it helps, I'm running Amarok from GNOME, in Ubuntu 8.04.

Not sure if this helps, but whenever Amarok stops working like this, Rhythmbox also stops working.  However, Rhythmbox doesn't crash; it just won't play any audio.

I have this exact same problem with 8.04 LTS running on a E6600, Nvidia 8800gts, GIGABYTE GA-EP35C-DS3R LGA 775 Intel P35, corsair xms.

Forgot to say I am using the xine engine.

Ubuntu... They set pulseaudio as default everywhere, but pulseaudio support in xine is absolutely messed up and needs a rewrite. Somewhere in the system-settings you have an option where to use which audio system. Go change them all to ALSA or esd and then (if it didn't happen automatically) change xine output in Amarok to ALSA.