Audio output consumes 100% cpu and no red lips

Bug #651267 reported by Barry Warsaw
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mumble (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: mumble

Ubuntu 10.10

A week ago, mumble 1.2.2 worked just fine on this machine using pulse audio and the default device. Now when I connect other people can hear me but I cannot hear anyone else. And I only see red lips for myself, not for anyone else. When I go to Settings -> Advanced -> Messages and click on a notification audio file, mumble freezes consuming 100% cpu. When I go through the audio wizard and click Next> in the audio tuning wizard, mumble freezes and consumes 100% cpu.

Audio output works just fine in other apps (e.g. Rhythmbox, browser videos, etc.). On my other Maverick laptop, mumble works just fine. I can't figure out what might have broken it in the last week.

Revision history for this message
ais523 (ais523) wrote :

#1268419 may or may not be a duplicate. If it is, changing to ALSA rather than PulseAudio may be a workaround.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.