I've just been reading my original report and it is not quite what I am experiencing now. Probably just poor observation at the time on my part, I expect, although I can't say that for certain.
The bad behaviour I am experiencing now is that when the machine is woken from sleep, it maxes out one core and has to be killed, although it still works as a sound server up to the point it is killed. I am not aware of any problem occurring with PulseAudio apart from the one I have just described here. -- pulseaudio starts to hog CPU https://bugs.launchpad.net/bugs/530643 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
