I have the same problem. I had this problem under a system upgraded to Hardy frpm Edubuntu Gutsy.
A fresh install of the Xubuntu nightly still has this problem. Steps to reproduce for me: - download, burn and install the Xubuntu Hardy Alternate 1386 disk - log in to your new system. install Amarok (and, Amarok's extra engines, and pulseaudio if requires) through synaptic. - Reboot just to prove that pulseaudio will absolutely never ever start, except from the command line - start Amarok - Preferences Menu -> Configure Amarok -> Engines - Select the engine "pulseaudio" and press OK - push play actual result: amarok crashes expected result: sample track plays workaround: - type "pulseaudio" in the console, and THEN try playing through Amarok and its "pulseaudio" engine option Further tests: - download the pulseaudio manager, device chooser and volume control - see if you can get the amarok stream to appear in volume control without starting the server from the command line - see if the manager is not completely useless without starting pulseaudio from the command line >By default, PulseAudio is not invoked as a system-wide daemon from the >initscript. It is invoked, per-user, >from gnome-session via ESounD compatibility. Not invoking it from the init script (if I understand what you're saying) makes sense because somewhere on the pulseaudio website it recommends running it on a per-user basis and not as a systemwide daemon (I think) So if gnome-session and ESounD are automatically starting pulseaudio, does that mean that in my gnome installation, I magically don't have those installed? :-P I don't understand any of this as I'm new to Linux but I think that it has not worked as it was supposed to across two installations on my test box. In any event, I have to start it from the command line - and that's a nuisance.... amarok's last crash cause I'd forgotten to start pulseaudio took out pidgin collaterally because of a pidgin plugin I was running. -- pulseaudio doesn't start https://bugs.launchpad.net/bugs/195728 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
