jack_ programs fail to exit cleanly

[skyflyer]

Describe the bug

jack_ tools error at the end.

Environment

• JACK Version:

❯ jackd --version
jackdmp version 1.9.19 tmpdir /tmp protocol 9

• Operating System: macOS Monetery 12.1

• Installation: from github release

Steps To Reproduce

• Started jack through QJackCtl with 48000 sampling rate and 1024 periods/frame
• When trying to invoke jack_ commands, they error with Cannot read socket fd = 9 err = Socket is not connected

A couple of examples:

❯ jack_lsp
system:capture_1
system:playback_1
system:playback_2
Cannot read socket fd = 9 err = Socket is not connected
CheckRes error
JackSocketClientChannel read fail

❯ jack_rec -f test.wav -d 100 system:capture_1
disk thread finished
JackMachSemaphore::TimedWait name = js501.jackrec usec = 9223372036854775807 err = (os/kern) object terminated
JACK shut down, exiting ...
Cannot read socket fd = 7 err = Operation timed out
Could not read result type = 24
SuspendRefNum error
JackClient::Execute error name = jackrec

❯ jack_samplerate
48000
Cannot read socket fd = 9 err = Socket is not connected
CheckRes error
JackSocketClientChannel read fail
JACK shut down, exiting ...

❯ jack_bufsize
1024
Cannot read socket fd = 9 err = Socket is not connected
CheckRes error
JackSocketClientChannel read fail
JACK shut down, exiting ...

❯ jack_freewheel n
Cannot read socket fd = 9 err = Socket is not connected
CheckRes error
JackSocketClientChannel read fail
JACK shut down, exiting ...

❯ jack_thru
jack_connect called with a NULL port name
cannot connect input ports
^CJackMachSemaphore::TimedWait name = js501.jack_thru usec = 9223372036854775807 err = (os/kern) object terminated
SuspendRefNum error
JackClient::Execute error name = jack_thru
Cannot read socket fd = 9 err = Socket is not connected
CheckRes error
JackSocketClientChannel read fail

Expected vs. actual behaviour

The jack_ commands should exit cleanly. They don't currently.

[falkTX]

well nothing is working at all in there, so yeah every command fails.

try starting jackd manually outside of qjackctl, in dummy mode in order to avoid any conflicts, like so:

jackd -d dummy

then see if the tools still dont work. thanks

[skyflyer]

@falkTX, yep, it is the same with dummy backend:

❯ jack_lsp
system:capture_1
system:capture_2
system:playback_1
system:playback_2
Cannot read socket fd = 9 err = Socket is not connected
CheckRes error
JackSocketClientChannel read fail

Not a big deal, but annoying. The commands work (you can see the output, and jack_rec -f test.wav -d 100 system:capture_1 records 100 seconds of audio, but... ends with an error.