[SOLVED]Jack doesn't work anymore

Question

Good day people,
It seems that Jack stopped working all of a sudden. Well, it's not really all of a sudden, it hasn't been working for 3 months or so, but before that it worked just fine and I did not change any setting since then. I didn't post before because I don't really use JACK too often but now it seems like I'll be going to need it.
The package I'm using is jack2 from the community repository, not jack2-dbus or jack or any other package, although I've tried them with the same results.
First, let's try to start jack the old fashioned way
$jack_control start
it results in
DBus exception: org.jackaudio.Error.Generic: Failed to open server
...ook. Let's try an even older fashion way.
$jackd -d alsa
The output is:
jackdmp 1.9.8
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2011 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
could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
jack_get_descriptor returns null for 'jack_firewire.so'
could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
JACK server starting in realtime mode with priority 10
Jack: Create non RT thread
Jack: ThreadHandler: start
Jack: JackDriver::Open capture_driver_name = hw:0
Jack: JackDriver::Open playback_driver_name = hw:0
Jack: Check protocol client = 8 server = 8
Jack: JackEngine::ClientInternalOpen: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 1024
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
control device hw:0
control device hw:0
audio_reservation_init
Failed to acquire device name : Audio0 error : Method "RequestRelease" with signature "i" on interface "org.freedesktop.ReserveDevice1" doesn't exist
Audio device hw:0 cannot be acquired...
Jack: ~JackDriver
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: ThreadHandler: exit
JackServer::Open() failed with -1
Jack: Succeeded in unlocking 82245916 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: Succeeded in unlocking 1012 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: cleaning up shared memory
Jack: cleaning up files
Jack: unregistering server `default'
Failed to open server
No luck this time, either. And before you ask, I tried giving jackd other parameters but it didn't change anything.
I now try Qjackctl. As soon as I open it, it says:
D-BUS: JACK server could not be started
Sorry
This is the error log:
11:31:23.797 Patchbay deactivated.
11:31:23.800 Statistics reset.
11:31:23.802 ALSA connection change.
11:31:23.819 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
11:31:23.994 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
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
11:31:24.016 ALSA connection graph change.
Thu Aug 23 11:31:23 2012: Starting jack server...
Thu Aug 23 11:31:23 2012: JACK server starting in realtime mode with priority 10
Thu Aug 23 11:31:23 2012: control device hw:0
Thu Aug 23 11:31:23 2012: control device hw:0
Thu Aug 23 11:31:23 2012: Acquired audio card Audio0
Thu Aug 23 11:31:23 2012: creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
Thu Aug 23 11:31:23 2012: control device hw:0
Thu Aug 23 11:31:23 2012: configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
Thu Aug 23 11:31:23 2012: ALSA: final selected sample format for capture: 32bit integer little-endian
Thu Aug 23 11:31:23 2012: ALSA: use 2 periods for capture
Thu Aug 23 11:31:23 2012: ALSA: final selected sample format for playback: 32bit integer little-endian
Thu Aug 23 11:31:23 2012: ALSA: use 2 periods for playback
Thu Aug 23 11:31:23 2012: [1m[31mERROR: ALSA: cannot set hardware parameters for playback[0m
Thu Aug 23 11:31:23 2012: [1m[31mERROR: ALSA: cannot configure playback channel[0m
Thu Aug 23 11:31:23 2012: [1m[31mERROR: JackTemporaryException : now quits...[0m
Thu Aug 23 11:31:23 2012: [1m[31mERROR: Cannot initialize driver[0m
Thu Aug 23 11:31:23 2012: [1m[31mERROR: JackServer::Open() failed with -1[0m
Thu Aug 23 11:31:23 2012: [1m[31mERROR: Failed to open server[0m
11:32:54.690 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
Ok, let's now uncheck "Enable D-Bus interface" and try again, maybe I'll have more luck. No, it seems I don't.
This is the message log:
11:34:17.340 Patchbay deactivated.
11:34:17.345 Statistics reset.
11:34:17.347 ALSA connection change.
11:34:17.356 JACK is starting...
11:34:17.356 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p1024 -n2
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
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
11:34:17.361 ALSA connection graph change.
could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
jack_get_descriptor returns null for 'jack_firewire.so'
could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
jackdmp 1.9.8
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2011 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 realtime mode with priority 10
11:34:17.396 JACK was started with PID=2499.
Jack: Create non RT thread
Jack: ThreadHandler: start
Jack: playback device hw:0
Jack: capture device hw:0
Jack: apparent rate = 48000
Jack: frames per period = 1024
Jack: JackDriver::Open capture_driver_name = hw:0
Jack: JackDriver::Open playback_driver_name = hw:0
Jack: Check protocol client = 8 server = 8
Jack: JackEngine::ClientInternalOpen: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 1024
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
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 cannot be acquired...
Jack: ~JackDriver
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: ThreadHandler: exit
JackServer::Open() failed with -1
Jack: Succeeded in unlocking 82245916 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: Succeeded in unlocking 1012 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: cleaning up shared memory
Jack: cleaning up files
Jack: unregistering server `default'
Failed to open server
11:34:17.533 JACK was stopped with exit status=255.
11:34:19.562 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
I've tried deleting all jack config files, changing settings and before you ask, I've tried with and without pulseaudio (which got along with Jack just fine before everything broke). It seems to be a d-bus problem at first but it gives me issues with d-bus disabled as well. I've read A LOT of forum posts and mailing lists before posting here and I can tell you that none of the solutions that worked for others worked for me, and many just gave up.
I don't have any audio/drive issues and as I said, my computer used to run Jack2 just fine. The output of cat /proc/asound/cards is
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf0400000 irq 45
It seems strange to me that jack2 and jack2-dbus act exactly the same way in regards to dbus but dbus is just one of the several problems, it seems. Right now I'm running my music production thanks to a live Ubuntu Studio stick (the horror, I know) and after extensive research I feel I'm out of ideas. I mean, I uninstalled jack and deleted all config files and it still doesn't go back to normal, what can I do? I suspect my problem may be related to improper configuration of something in /etc/ but I didn't touch anything audio-related in ages and as I said, jack used to work with the same configuration. It seems to have problem accepting that my sound card is hw:0, maybe. I don't know, it makes me crazy. Can someone help me? Thanks.
Edit: The problem is solved, checkout my last reply to this thread for the solution.
Last edited by VisionsOf (2012-08-28 11:30:13)

Answer 1

Hi, I'm having a similar issue. I've been using jack2 as the main audio server with pulseaudio routed through it for more than a year with no issues until a couple of weeks ago when after a power failure jack just stopped working.
After double checking my conf (found nothing strange, again, I'm using jack in normal production for over a year and havent touched conf in a while) and downgrading kernels and jack with no success  I realized that if I suspended the PC, and tryed to start jack after resuming it, there wasnt any problems at all!!? Jack works!
Something similar happens in my laptop (same setup), but in this case jack fails to start only the first try, on the 2nd try it will start flawlesly.
Could it be related to systemctl?? dbus?? (the same happens with Dbus interface enabled or not)
Pulseaudio? I've read in forums there are some issues between jack and pulseaudio, and in fact I can see pulseaudio “dead” in both situations (jack working and not)
systemctl status pulseaudio
pulseaudio.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
I guess I'm still not getting right the new Systemd method or the pulseaudio method or both
Here's the log of Qjackctl when it fails (same result starting jack from command line)
ERROR: JackProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
ERROR: Driver is not running
ERROR: Cannot open client name = dbusapi
ERROR: failed to create dbusapi jack client
17:49:51.668 ALSA connection graph change.
17:49:51.698 ALSA connection graph change.
17:49:58.744 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info.
Client name = qjackctl conflits with another running client
Any hints will be very welcome!
Cheers!