New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in Mumble 1.3.0_3 #20858
Comments
Looks like Mumble 1.3.0 always tries to connect to JACK on startup regardless of backend settings. EDIT: Sorry for the breakage. |
System
Void 5.6.2_1 x86_64 GenuineIntel uptodate rFFF
Mumble 1.3.0_3
Expected behavior
Mumble starts up in a second or so (on a SATA SSD)
Actual behavior
Significantly delayed start up, due to mumble trying to connect to the JACK daemon when it isn't installed w/ output
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
exec of JACK server (command = "/usr/bin/jackd") failed: No such file or directory
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
2020-04-10 18:04:11.864 JackAudioSystem: unable to open client due to 2 errors:
2020-04-10 18:04:11.864 JackAudioSystem: JackFailure - overall operation failed
2020-04-10 18:04:11.864 JackAudioSystem: JackServerFailed - unable to connect to the JACK server
Steps to reproduce the behavior
Upgrade to mumble 1.3.0_3
The text was updated successfully, but these errors were encountered: