Jack says it's running but Apps say it isn't.

Still new to all of this? Feel free to post in any of the subforums on this site, but in this subforum newbie questions are especially encouraged!

Moderators: MattKingUSA, khz

Post Reply
Studiohead
Established Member
Posts: 9
Joined: Fri Sep 25, 2020 6:35 pm
Has thanked: 2 times
Been thanked: 1 time

Jack says it's running but Apps say it isn't.

Post by Studiohead »

My problem is that I’m not sure if Jack is running or not.

Jack seems to be starting OK - QJackctl and Ubuntu Studio Controls both state that it’s running but when I open Guitarix a message states that Jack is not running and Rakarrack crashes on opening.

I’m using a Windows 7 & era laptop now running Linux Mint 20.1 Ulyssa with a low latency kernel.

Any ideas?

See the error report created when I tried to open rakarrack below.


09:37:40.884 Statistics reset.
09:37:40.931 ALSA connection change.
09:37:40.938 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
09:37:41.003 JACK connection change.
09:37:41.010 Client activated.
09:37:41.010 Patchbay deactivated.
Wed May 12 09:37:40 2021: New client 'qjackctl' with PID 4024
09:37:48.665 JACK connection graph change.
09:37:48.889 ALSA connection graph change.
09:37:48.912 ALSA connection change.
09:37:48.923 JACK connection graph change.
09:37:48.923 ALSA connection graph change.
Wed May 12 09:37:48 2021: New client 'rakarrack' with PID 4036
09:37:49.116 JACK connection change.
09:37:49.204 JACK connection graph change.
09:37:49.210 ALSA connection graph change.
09:37:49.320 JACK connection change.
09:37:49.321 ALSA connection change.
Wed May 12 09:37:49 2021: Connecting 'rakarrack:out_1' to 'system:playback_1'
Wed May 12 09:37:49 2021: Connecting 'rakarrack:out_2' to 'system:playback_2'
Wed May 12 09:37:49 2021: Connecting 'system:capture_1' to 'rakarrack:in_1'
Wed May 12 09:37:49 2021: Connecting 'system:capture_1' to 'rakarrack:in_2'
09:37:52.525 XRUN callback (1).
Wed May 12 09:37:52 2021: ERROR: JackEngine::XRun: client = rakarrack was not finished, state = Triggered
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
09:37:53.171 ALSA connection graph change.
09:37:53.179 JACK connection graph change.
09:37:53.341 JACK connection change.
09:37:53.344 ALSA connection change.
09:37:53.344 XRUN callback (2 skipped).
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:52 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: ERROR: JackEngine::XRun: client = rakarrack was not finished, state = Triggered
Wed May 12 09:37:53 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: ERROR: JackEngine::XRun: client = rakarrack was not finished, state = Triggered
Wed May 12 09:37:53 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed May 12 09:37:53 2021: Disconnecting 'system:capture_1' from 'rakarrack:in_1'
Wed May 12 09:37:53 2021: Disconnecting 'system:capture_1' from 'rakarrack:in_2'
Wed May 12 09:37:53 2021: Disconnecting 'rakarrack:out_1' from 'system:playback_1'
Wed May 12 09:37:53 2021: Disconnecting 'rakarrack:out_2' from 'system:playback_2'
Wed May 12 09:37:53 2021: ERROR: Failed to find port 'rakarrack:in_1' to destroy
Wed May 12 09:37:53 2021: ERROR: Failed to find port 'rakarrack:in_2' to destroy
Wed May 12 09:37:53 2021: ERROR: Failed to find port 'rakarrack:aux' to destroy
Wed May 12 09:37:53 2021: ERROR: Failed to find port 'rakarrack:in' to destroy
Wed May 12 09:37:53 2021: ERROR: Failed to find port 'rakarrack:out_1' to destroy
Wed May 12 09:37:53 2021: ERROR: Failed to find port 'rakarrack:out_2' to destroy
Wed May 12 09:37:53 2021: ERROR: Failed to find port 'rakarrack:MC out' to destroy
Wed May 12 09:37:53 2021: Client 'rakarrack' with PID 4036 is out
tavasti
Established Member
Posts: 2047
Joined: Tue Feb 16, 2016 6:56 am
Location: Kangasala, Finland
Has thanked: 369 times
Been thanked: 208 times
Contact:

Re: Jack says it's running but Apps say it isn't.

Post by tavasti »

Looks like jack is running, but rakarrak is crashing, for some other reason.

What is accurate message Guitarix says?

Linux veteran & Novice musician

Latest track: https://www.youtube.com/watch?v=ycVrgGtrBmM

Studiohead
Established Member
Posts: 9
Joined: Fri Sep 25, 2020 6:35 pm
Has thanked: 2 times
Been thanked: 1 time

Re: Jack says it's running but Apps say it isn't.

Post by Studiohead »

Guitarix refuses to open a message says: Jack is not running.

Hydrogen works.

Thanks.
merlyn
Established Member
Posts: 1392
Joined: Thu Oct 11, 2018 4:13 pm
Has thanked: 168 times
Been thanked: 247 times

Re: Jack says it's running but Apps say it isn't.

Post by merlyn »

Studiohead wrote:... QJackctl and Ubuntu Studio Controls ...
You don't need them both.
Wed May 12 09:37:40 2021: New client 'qjackctl' with PID 4024
That means JACK was already running when you opened QjackCtl.
09:37:40.938 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
That means you're using jackdbus which may start JACK when you log in. JACK is definitely started. Why doesn't Guitarix recognise it? To work out why try having the simplest setup possible.
Studiohead
Established Member
Posts: 9
Joined: Fri Sep 25, 2020 6:35 pm
Has thanked: 2 times
Been thanked: 1 time

Re: Jack says it's running but Apps say it isn't.

Post by Studiohead »

I uninstalled and reinstalled Guitarix and Rakarrack and now they work.

Prior to this they’d refused to work yet Jack was running, this happened after Jack refused to start, I managed to get it to start again but the above 2 x apps seemed to become uncoupled from Jack after the re-start.
Post Reply