Skip to content
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

Closed
Max-FT opened this issue Apr 10, 2020 · 1 comment · Fixed by #20862
Closed

Regression in Mumble 1.3.0_3 #20858

Max-FT opened this issue Apr 10, 2020 · 1 comment · Fixed by #20862

Comments

@Max-FT
Copy link

Max-FT commented Apr 10, 2020

System

  • xuname:
    Void 5.6.2_1 x86_64 GenuineIntel uptodate rFFF
  • package:
    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

@ScrelliCopter
Copy link
Contributor

ScrelliCopter commented Apr 11, 2020

Looks like Mumble 1.3.0 always tries to connect to JACK on startup regardless of backend settings.
Seems this was fixed upstream in mumble-voip/mumble#3990 in master.
I'll try patching 1.3.0 with this change and see if it fixes the problem.

EDIT:
I wrote some sed to set bJackStartServer and bJackAutoConnect to false, unfortunately this does not seem to stop Mumble trying to connect to jack on startup regardless of the backend setting and if jack is even installed.
For now it seems best to revert #20840 or make it a template option (off by default) for jack users like myself.

Sorry for the breakage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants