I was running ardour just fine and now it can’t start jack, this is what it gives me
Ardour could not start JACK
There are several possible reasons:
You requested audio parameters that are not supported…
JACK is running as another user.
Please consider the possibilities, and perhaps try different parameters.
-I open up jack and this is what I get-
Could not connect to JACK server as client.
Overall operation failed.
Unable to connect to server.
Please check the messages window for more info.
13:53:28.133 Patchbay deactivated.
13:53:28.645 Statistics reset.
13:53:28.668 Startup script…
13:53:28.668 artsshell -q terminate
13:53:28.673 ALSA connection graph change.
13:53:29.633 Startup script terminated with exit status=256.
13:53:29.634 JACK is starting…
13:53:29.634 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver …
SSE2 detected
apparent rate = 44100
creating alsa driver … hw:0|hw:0|1024|2|44100|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
no message buffer overruns
13:53:29.845 JACK was started with PID=7128.
13:53:29.847 ALSA connection change.
13:53:29.850 JACK was stopped successfully.
13:53:29.850 Post-shutdown script…
13:53:29.851 killall jackd
jackd: no process killed
13:53:30.307 Post-shutdown script terminated with exit status=256.
13:53:31.876 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
please If anyone can help me I would really like to figure this out thank you.
I’ve got a similar problem, but in Jack Messages window I get
14:36:39.189 Patchbay deactivated.
14:36:39.193 Statistics reset.
/usr/local/bin/jackd: error while loading shared libraries: libjackserver.so.0: cannot open shared object file: No such file or directory
14:36:39.253 ALSA connection graph change.
14:36:39.508 ALSA connection change.
14:36:44.334 Startup script…
14:36:44.334 artsshell -q terminate
/usr/local/bin/jackd: error while loading shared libraries: libjackserver.so.0: cannot open shared object file: No such file or directory
14:36:44.748 Startup script terminated with exit status=256.
14:36:44.748 JACK is starting…
14:36:44.748 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver …
apparent rate = 44100
creating alsa driver … hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
14:36:44.762 JACK was started with PID=6797.
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
14:36:46.848 Could not connect to JACK server as client. - Overall operation failed. Please check the messages window for more info.
/usr/local/bin/jackd: error while loading shared libraries: libjackserver.so.0: cannot open shared object file: No such file or directory
I tried reinstalling Jack libraries but it still doesn’t work, any ideas?
@mkloch87: You seem to have jack installed both in /usr/bin and /usr/local/bin: 14:36:44.748 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2 and /usr/local/bin/jackd: error while loading shared libraries. That’s never a good idea.
Are you running a qjackctl that was compiled against a jack in /usr/local that you since has removed ?
Yeah you were right, I’ve got jackd in both /usr/local/bin and /user/bin. How do I fix that? Would that be enough to delete one of them? And if yes, which one should I delete? Can’t really say anything about qjackctl, I think it came with my system (that’s jack control we’re talking about, right?).
Check out which jack qjackctl is linked against by running
ldd which qjackctl | grep jack
If it’s (as I think) linked against /usr/local/lib/libjack… you go to /usr/lib, create a JACKBAK dir and move libjack* to that dir. Do the same in /usr/bin and move the jack* files to that dir. Try running things again.
If that doesn’t work put the files from the JACKBAK dirs back and do the same thing with the files in the /usr/local dirs.
when I typed fuser in the terminal it gave me this
No process specification given
Usage: fuser [ -a | -s | -c ] [ -n SPACE ] [ -SIGNAL ] [ -kimuv ] NAME…
[ - ] [ -n SPACE ] [ -SIGNAL ] [ -kimuv ] NAME…
fuser -l
fuser -V
Show which processes use the named files, sockets, or filesystems.
-a display unused files too
-c mounted FS
-f silently ignored (for POSIX compatibility)
-i ask before killing (ignored without -k)
-k kill processes accessing the named file
-l list available signal names
-m show all processes using the named filesystems
-n SPACE search in this name space (file, udp, or tcp)
-s silent operation
-SIGNAL send this signal instead of SIGKILL
-u display user IDs
-v verbose output
-V display version information
-4 search IPv4 sockets only
-6 search IPv6 sockets only
- reset options
a process is using your audio device. The /dev/snd/pcmC0D0p is called a device node, it is created by ALSA (the low level audio layer that is part of the linux kernel). Applications that want to talk to the audio device will use the device node. A program like jack would like to grab your device when you start it but something is already using it exclusively. Paul’s tip allows you to know what is using your audio device. fuser returns the process ID (for each running process, there’s an ID number). Now that you know these IDs, you can kill these processes:
sudo kill -9 5765 7510 11758
If you have firefox or other browser opened, the chance is that it will be killed because as someone said before, it could well be that goddamned flashplugin. As soons as you watch a flash video through this plugin, there’s no way you’ll be able to start jack after that unless you exit your web browser. You are warned
Paul’s lsof/fuser commands are used to find out what process is hogging the soundcard. When you know that you need to kill that process or stop it in some other way to be able to use jack.
I ran ‘lsof | grep dev/snd’ while playing some music and it showed
@calimerox: if you ever see the “device in use” message, you need to recheck with lsof/fuser. If you see some other message, well, its a different problem …
oops, its getting late and i do stupid mistakes… actually jack2 config made jack running in dummy mode, so it just pretended to run fine, i still get the same message when i turn to alsa. …
so i get the device in use message, but checking doesnt tell me.
or did i write the command wrong?
thats weird, for a really long time i never had trouble with jack…
here the complete qjackctl output again:
02:11:19.323 Patchbay deactivated.
02:11:19.357 Statistics reset.
02:11:19.359 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
02:11:34.063 Startup script…
02:11:34.064 artsshell -q terminate
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
sh: artsshell: not found
02:11:34.467 Startup script terminated with exit status=32512.
02:11:34.468 JACK is starting…
02:11:34.470 /usr/bin/jackd -r -p128 -t5000 -dalsa -dhw:0,0 -r48000 -p128 -n2 -s
no message buffer overruns
no message buffer overruns
jackdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in non-realtime mode
02:11:34.528 JACK was started with PID=3458.
control device hw:0
control device hw:0
audio_reservation_init
Failed to acquire device name : Audio0 error : Device or resource busy
Audio device hw:0,0 cannot be acquired, trying to open it anyway…
creating alsa driver … hw:0,0|hw:0,0|128|2|48000|0|0|nomon|swmeter|soft-mode|32bit
control device hw:0
Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xee240000 irq 47
the capture device “hw:0,0” is already in use. Please stop the application using it and run JACK again
Cannot initialize driver
JackServer::Open() failed with -1
Failed to start server
02:11:34.609 JACK was stopped with exit status=255.
02:11:34.609 Post-shutdown script…
02:11:34.610 killall jackd
jackd: no process found
02:11:35.020 Post-shutdown script terminated with exit status=256.
02:11:36.653 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
maybe I messed up something before jack tries to connect?
@calimerox: as i noted, any time you see the message about the device being busy, you must run lsof/fuser to determine what is using it (if you don’t know).
@calimerox
In post #18 you had exile, a music player, running. I might be wrong but I guess you had started it manually, and had it open while you were trying to start jack.
You need to shut down any music or video player, including any flash player you might be running in a browser, before you attempt to start jack.
The best thing is probably to reboot and try to start jack the first thing you do.
If that doesn’t work run ‘lsof | grep dev/snd’ to see what’s there and see if you can somehow prevent that process from autostarting.
hmm i tried all this but no luck… I dont know what went wrong…
after using the fuser command jack still doesn´t start, I also rechecked the jack preparation on lucid (audio group, rtprio and so on) but somehow… thats the konsole:
no message buffer overruns
no message buffer overruns
JACK server starting in non-realtime mode
control device hw:0
control device hw:0
audio_reservation_init
Acquire audio card Audio0
creating alsa driver … hw:0|hw:0|512|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xee240000 irq 17
the capture device “hw:0” is already in use. Please stop the application using it and run JACK again
Cannot initialize driver
JackServer::Open() failed with -1
Failed to start server
