Jack won't start

I just switched distros, but it’s not that big a a jump… I went from Arch to Chakra. I copied my ~/.jackdrc and .config/rncbc/QjackCtl files over from the old installation. I configured realtime priority, rebooted, and went to launch Jack but got this:

13:13:41.219 Patchbay deactivated.
13:13:41.221 Statistics reset.
13:13:41.222 ALSA connection change.
13:13:41.281 Startup script…
13:13:41.281 artsshell -q terminate
13:13:41.286 ALSA connection graph change.
sh: artsshell: command not found
13:13:41.687 Startup script terminated with exit status=32512.
13:13:41.687 JACK is starting…
13:13:41.687 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -n2 -D -Chw:0
13:13:41.689 JACK was started with PID=4921.
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O’Quinn, Torben Hohn and others.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 3040488
JACK compiled with System V SHM support.
loading driver …
apparent rate = 48000
creating alsa driver … hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
the playback device “hw:0” is already in use. Please stop the application using it and run JACK again
cannot load driver module alsa
13:13:41.713 JACK was stopped successfully.
13:13:41.713 Post-shutdown script…
13:13:41.713 killall jackd
jackd: no process found
13:13:42.120 Post-shutdown script terminated with exit status=256.
13:13:43.899 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

I’m using an Maudio Delta44 soundcard.

the playback device "hw:0" is already in use. Please stop the application using it and run JACK again

Pretty well sums it up, something is already using the hardware you are trying to get Jack to use.


Yeah, but as near as I can determine everything is turned off.

There is a pcm device in your /dev/snd/ directory, likely labeled pcmC0D0p and pcmC0D0c, run fuser on that, and it will give you the PID of the process accessing it. You can then look this up via a ps -A and see what the process is.


I have both pcmC0D0p and pcmC0D0c. I ran fuser (which I really don’t know what I’m doing with) on both. “fuser /dev/snd/pcmC0D0c” returned no output. “fuser /dev/snd/pcmC0D0p” returned “1997m”. “ps -A 1997m” returned a syntax error.

No you would just do
ps -A
And look up what matches the process ID 1997

Alternatively you could do
ps -A | grep 1997
which accomplishes the same thing.


Okay, got it… it was knotify, of all things! Jack is running. Thanks so much!