I believe you misread my report. Rhythmbox's code clearly gets notified that its connection to pulse has been terminated. This is very easy to provoke if you follow my steps.
The error-handler-function of rhythmbox prints out the message - but it doesn't handle it, because there is no code which handles this error message. I haven't opened a bug about it crashing, but about it freezing --- I discovered this while pulse-audio stopped functioning on my workstation, and I had to kill my pulse-processes "anything" work (several applications was frozen)... Most applications behaved normally after the kill, but what I noticed is that rhythmbox was one out of two applications which didn't handle the (unexpected) kill properly. (On a side note: the other one is pidgin, which already had a bug filed for it - Bug 238963 --- the behaviour isn't identical, as rhythmbox only freezes --- it does not consume 100% cpu) I'm quite confident that this bug is fixable by adding a few lines to the error handling function (rb_shell_player_error) in shell/rb-shell- player.c ... If I could manage to get rhythmbox to compile properly in the first place, I would have submitted a patch. -- Rhythmbox does not handle a sudden/unexpected dissappearance of pulse server properly https://bugs.launchpad.net/bugs/258032 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
