Sorry, I should have gotten back to this sooner. My point with this bug report was not that I had my settings set properly for the exact setup (I do, but I have to remember to start pulseaudio, currently), but that Rhythmbox dies. A program should /not/ just die; Rhythmbox should *gracefully* handle the error and not "just crash".
Juxtapose this behavior with, say, Amarok. Amarok deals with no sound- server much more gracefully. I'll give you that it "could be an ALSA configuration issue", but if so, it's a parallel issue. This may be related as well: if I'm using Rhythmbox and switch to a tty (e.g. Ctrl+Alt+F1), the connection gets broken (or something) and Rhythmbox dies. Again, juxtapose this behavior with Amarok: it doesn't die, and continues to play sound normally. Suggest not closing this bug, or otherwise help me better articulate where to find the bug *in Rhythmbox*. -- no sound-server available, rhythmbox freezes https://bugs.launchpad.net/bugs/244324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
