14:16:21.205 Could not connect to JACK server as client. -

**timtincher** · April 30th, 2012

I was just trying to get Jack to start and this happened:

Code:

14:16:13.931 Patchbay deactivated.
14:16:13.934 Statistics reset.
14:16:13.938 ALSA connection change.
14:16:13.945 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
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
14:16:17.611 D-BUS: JACK server could not be started. Sorry
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
Mon Apr 30 14:16:17 2012: Starting jack server...
Mon Apr 30 14:16:17 2012: JACK server starting in realtime mode with priority 10
Mon Apr 30 14:16:17 2012: [1m[31mERROR: Cannot lock down 82241434 byte memory area (Cannot allocate memory)[0m
Mon Apr 30 14:16:17 2012: control device hw:0
Mon Apr 30 14:16:17 2012: control device hw:0
Mon Apr 30 14:16:17 2012: [1m[31mERROR: Failed to acquire device name : Audio0 error : Cannot allocate memory[0m
Mon Apr 30 14:16:17 2012: [1m[31mERROR: Audio device hw:0 cannot be acquired...[0m
Mon Apr 30 14:16:17 2012: [1m[31mERROR: Cannot initialize driver[0m
Mon Apr 30 14:16:17 2012: [1m[31mERROR: JackServer::Open() failed with -1[0m
Mon Apr 30 14:16:17 2012: [1m[31mERROR: Failed to open server[0m
Mon Apr 30 14:16:19 2012: Saving settings to "/home/tim/.config/jack/conf.xml" ...
14:16:21.205 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

;__________; What do I do?

**EnkiduinNZ** · May 23rd, 2012

Try this. Look at the file .jackdrc in your home directory. Use that command to start jackd from the command line. Then start qjackctl. It works for me!

Cliff

**b2wojo** · May 27th, 2012

Had the same error and running jackd from the command line worked. I noticed in the QjackCtl messages the line "control device hw:0" even though I had changed the setup to use my USB sound card device hw:2.

By blacklisting my on board sound card:
adding these lines to /etc/modprobe.d/blacklist.conf

# on board sound card (using USB)
blacklist snd_hda_intel

And commenting out all the lines in /etc/modprobe.d/alsa-base.conf that keep snd-usb-audio from being loaded as the first soundcard:

#options snd-usb-audio index=-2

After restart I got a new error from QjackCtl:
ATTENTION: The playback device "hw:0" is already in use. Please stop the application using it and run JACK again

Able to workaround that one by removing the sound icon:
sudo apt-get remove indicator-sound

QjackCtl now works to start jackd but probably should have stopped at it works from the command line as suggested.

**chkneater** · May 30th, 2012

The message "Qjackctl is already in use" is usually a good sign that Jack was improperly shut down at some point and qjackctl is still running in the background

killall qjacktcl

and just in case : killall jackd

you might need to sudo but I doubt it

Also, I just found out that when I run qjackctl with sudo permissions versus jackd from the menu, I have NO errors at all with the server OR with socket err. I also checked the tab under Settings that says "configure as temporary server". Not sure if that last step is necessary, but if you can run "sudo qjackctl" with less problems then Jack is not getting Root access to key files for some reason.

**chkneater** · May 31st, 2012

Was that from the terminal or from the menu? I just found out myself that running qjackctl as root solved all the socket err and connected right to the server. Try that and tell what happens.

**Emilie** · March 20th, 2013

Originally Posted by EnkiduinNZ

Try this. Look at the file .jackdrc in your home directory. Use that command to start jackd from the command line. Then start qjackctl. It works for me!

Cliff

This totally worked for me, I guess jackd just wasn't getting started properly (qjackctl starts jackdbus but not jackd...). Kind of annoying to have to do every time I need jack, but at least it works. Thanks!