Page 1 of 1
Help me understand these QjackCtl errors?
Posted: Tue Aug 15, 2023 9:55 pm
by ThatJackElliott
Hi
I am launching QjackCtl from the command line like this:
Code: Select all
/usr/bin/qjackctl --active-patchbay= /home/kpov_tech/Desktop/Settings/KPOV_Test_Live_MCR_In.xml &
and I am getting these errors:
Code: Select all
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
JACK then starts, but I'd like to understand those errors.
Thank you!
Re: Help me understand these QjackCtl errors?
Posted: Wed Aug 16, 2023 12:31 am
by Impostor
I always get those messages too.
I guess that a shared memory read-write pointer (*) for jack cannot yet be initialised if jack server is not started yet, and that it's a bit impatient. In my qjackctl log, those messages occur (twice even!) in the same millisecond as the message that the jack server has started.
(*)don't ask me what that is..
Code: Select all
02:19:55.918 D-BUS: JACK server was started (org.jackaudio.service aka jackdbus).
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
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
Re: Help me understand these QjackCtl errors?
Posted: Wed Aug 16, 2023 9:33 am
by merlyn
They're not errors as such. Conceivably JACK could be started before QjackCtl, so QjackCtl tries to connect to JACK when it's launched. If JACK isn't started, those are the messages. If QjackCtl has been set to start JACK when it's launched, you'll get those messages, then the JACK startup messages.