1.3.1 when it's ready rather than trying to release the release
candidate.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874231
Title:
mu
** Bug watch added: Debian Bug tracker #952742
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952742
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874231
Title:
mumble freezes all audio
80d93aab3eec9796e1cb8606c5f3c089d64eca
Mumble upstream is preparing a 1.3.1 bugfix release and recently uploaded an rc1
release candidate which I'm evaluating to see if it's releasable.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
--
You received this bug notification because you are
of TLS that have perfect
forward secrecy, but Mumble 1.2 with Qt 4 is not, and that's independent of the
particular versions of OpenSSL that are used. i.e. this isn't a limitation of
the OpenSSL version, it's a limitation of the SSL library in Qt 4.
-- Chris
--
Chris Knadle
chris.kna...@cored
ve libqt5sql5-mysql as another option the user could choose manually.
Another option would be to keep Depends: libqt5sql5-sqlite as-is and then add a
Suggests: libqt5sql5-mysql for mumble-server.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
--
You received this bug notification because y
d like to figure out a way to do this that isn't difficult for the
user to use (and that won't create a support headache).
Let me know if you're willing to test a Mumble package (that isn't in
the Ubuntu or Debian repos) that attempts to do this.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
The git commit referenced is included in mumble 1.2.12-1ubuntu1 (and
probably versions before)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212743
Title:
mumble crashes on multi-speaker setups
"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 this particular bug.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346431
Title:
Mumble server does not accept connections when started
I think I've found a workaround, though it defies logic. In /etc
/mumble-server.ini set:
host=::
which will work for both IPv6 and IPv4 -- or to limit use to only IPv4,
use a setting of:
host=0.0.0.0
[This works on Debian with mumble-1.2.8-2 at least.]
The reason this makes no sense
Yes, it started on boot (and reboot) by default.
And yes, I'm getting Server listening on [::]:64738 everytime, so I'm
not hitting the bug. :-/
** Attachment added: mumble-server-ubuntu.log
I don't know how I got to be the maintainer of this package in Ubuntu; I
assume it's becaue I'm the maintainer for the pacakge in Debian.
I've installed Ubuntu 14.04 LTS Desktop edition into a VirtualBox VM and
am not able to reproduce this bug, regardless of whether I modify the
Yep, that duplicated the bug; mumble-server will start, does not show Server
Listening, and indeed 'netstat -tpln' shows it's listening only locally and on
a different port:
tcp 0 0 127.0.0.1:6502 0.0.0.0:* LISTEN2360/murmurd
That's the Ice port that is shown in the log:
Public bug reported:
Back in June, version 1.2.3-349-g315b5f5-1 of the mumble source package
in Debian removed support for CELT and also introduced a subtle but
problematic setting in the mumble-server.ini file opusthreshold=1
which caused mumble-server to switch to the Opus codec if only 1% of
14 matches
Mail list logo
