Ubuntu
mumble package

mumble freezes in audio tuning wizard

Bug #1268419 reported by ais523 on 2014-01-12

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	mumble (Fedora)	New	Undecided	Unassigned
	mumble (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

When using the Audio Tuning Wizard, Mumble freezes with 100% CPU usage after clicking on "Next" on the "Device selection" screen (the first screen on which settings can be changed). Expected behaviour is for it to move to the next screen of the wizard. The notification area shows red lips when this operation is performed.

I went through this wizard during initial setup of Mumble, and noticed nothing unusual; this problem only occurred upon attempting to reconfigure the audio on a subsequent use.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: mumble 1.2.3-349-g315b5f5-2.2ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Sun Jan 12 23:39:08 2014
ExecutablePath: /usr/bin/mumble
InstallationDate: Installed on 2009-12-14 (1490 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_GB
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: mumble
UpgradeStatus: Upgraded to saucy on 2013-11-06 (67 days ago)

Tags:

Revision history for this message

ais523 (ais523) wrote on 2014-01-12:

Dependencies.txt Edit (8.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (49.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (816 bytes, text/plain; charset="utf-8")

Revision history for this message

ais523 (ais523) wrote on 2014-01-12:

Further information: Mumble quits upon SIGTERM, it doesn't require a SIGKILL (indicating, most likely, an infinite loop).

Revision history for this message

ais523 (ais523) wrote on 2014-01-12:

I managed to work around this bug by changing both input and output to use ALSA rather than PulseAudio.

Revision history for this message

James Thomas (notjim09) wrote on 2014-05-03:

I have the same bug. strace shows sched_yield over and over and the cpu stays at 100%.

sched_yield() = 0
sched_yield() = 0
sched_yield() = 0
sched_yield() = 0
^C+++ killed by SIGINT +++

Revision history for this message

hyper_ch (bugs-launchpad-net-roleplayer) wrote on 2015-07-09:

I have the same issue on 15.10.

CPU ist not affected but it just freezes if I select Pulse Audio.

Revision history for this message

Joost (joost-van-weenen) wrote on 2016-01-13:

Same here on 15.10

strace also just shows "sched_yield() = 0"

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-01-13:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mumble (Ubuntu):
status:	New → Confirmed

Revision history for this message

Georg Sauthoff (g-sauthoff) wrote on 2016-12-22:

I can confirm this issue with mumble 1.2.11 on Fedora 25.

Steps to reproduce:

1. Attach external USB headset
2. Execute mumble audio-wizard and select pulseaudio + that USB headset
3. Quit the mumble client and detach external USB headset
4. Start mumble client and execute audio-wizard, again
5. Select pulseaudio + internal audio in/out (or just the default one)

actual results: mumble client doesn't make progress, it consumes 100 % CPU - i.e. it hangs

expected results: normal walk-through the wizard

Workaround: Removing the `[audio]` and `[pulseaudio]` sections from `~/.config/Mumble/Mumble.conf` before starting the mumble client helps. That means with those sections removed the mumble audio wizard doesn't hang anymore and can be used as expected.

This issue seems to be similar to https://sourceforge.net/p/mumble/bugs/750/

Revision history for this message

Georg Sauthoff (g-sauthoff) wrote on 2016-12-22:

Upstream Github issue: https://github.com/mumble-voip/mumble/issues/1819