Comment 2 for bug 1519015

"sched_yield() = 0". Huh. 0 is what's returned on success.

   http://linux.die.net/man/2/sched_yield

Seems related to threading. The mumble source code doesn't contain this call, so it's probably something being called by the Qt4 library.

The best thing I can suggest at the moment for trying to track this down further is to install the mumble-dbg package and to run mumble via a debugger like gdb. It'll give you a lot of confusing output but it's the best chance of figuring out what is making the sched_yield() call and/or what else is going wrong. When it gets stuck, see if you can get a "backtrace" and report the output to the bug.

Thanks.