I had the same problem. I would start Mumble, and it would lock (hang) when I
tried to connect to the server. The terminal output was as follows
AudioInput: 28527 bits/s, 48000 hz, 480 sample CELT
PulseAudio: Starting input
alsa_input.usb-Logitech_Logitech_USB_Headset-00-Headset.analog-mono
Based on what I've seen, I think it's a pulseaudio problem. I can
sometimes boot and mumble will work perfectly. After a short amount of
time, it refuses to recognize that I have a microphone and any other app
trying to use the microphone (such as Skype or jitsi) is distorted - as
if the input gain
Brief update. I just applied updates and gconf said it needed to restart
my machine, so I did so and started Mumble as the first program after
login, with PulseAudio still selected as the sound system for both input
and output. Lo and behold, it works perfectly.
This leads me to thinking (as sugge
Oddly, after getting it working with ALSA as described above, setting it
back to PulseAudio again is also now working. I haven't tried any other
applications that require access to the sound devices yet, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I just filed Bug #878952 and marked it as a duplicate of this - I'm not
sure if this is the best way to get apport information associated with
this bug, but upon using apport-collect 844347, launchpad suggested I
might not want to do that.
--
You received this bug notification because you are a m
I am experiencing the same issue. I hopped onto the upstream irc channel
and here are some snippets of the conversation:
hello, mumble 1.2.3-2ubuntu2 is hanging for me on startup, i get
stuck in the audio wizard. a quick strace shows that it's infinitely doing a
sched_yield() call
any further
Further progress - I started Mumble, then killed PulseAudio (which
doesn't seem to want to stay dead). With some trial and error I have
been able to have at least a brief conversation. Some combinations of
input and output ALSA device result in very choppy audio locally -
including the text messa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mumble (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844347
Title:
mumb
My experience is almost identical, except that when clicking the Connect
button I do see additional output in the terminal:
OpenSSL Support: 1 (OpenSSL 1.0.0e 6 Sep 2011)
SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
However, going into Mumble Configuration and selectin
