Comment 9 for bug 567636

I'm also getting this on a fresh Lucid install: Run mumble, select server, click "connect", mumble stops responding and consumes as much CPU as is available. If instead I run mumble, go through the audio wizard (I don't need to change any settings, just keep hitting Next) and then select the same server and connect, all works as it should. I had no problems running Mumble 1.2 on a fresh jaunty install (with mumble from the mumble PPA) on the precise same hardware a month or two ago. No hardware is being connected or disconnected at any point. Microphone input is on one card, speaker output is on another; previously this used the default jaunty sound system (alsa?), now it's going through pulseaudio.

I want to help get this fixed, so if anyone can tell me what information would be useful (alsa or pulseaudio settings dump, attaching to mumble with strace, etc.) and the command options to use, I'd be more than happy to post back information. I may also be able to reproduce the earlier jaunty install for comparison if needed.