Jack2-dbus Doesn't Start

AlecB · 2013-05-08 01:22:08

When I try to start Jack with

jack_control start

I get

--- start

And then, after a pause,

ERROR:dbus.proxies:Introspect error on :1.10:/org/jackaudio/Controller: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken

And then after another pause,

DBus exception: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

I'm using the jack2-dbus package from the repositories. I'm also running Alsa with Pulseaudio. I've tried rebooting and reinstalling jack, to no avail. Any ideas if it's a problem with dbus or jack? Thanks everyone

Last edited by AlecB (2013-05-08 01:25:22)

ooo · 2013-05-08 11:44:01

can you start jackd manually via command line or qjackctl? Also are you sure you have dbus-daemon running?

also it's possible that pulseaudio is blocking your audio-device preventing jackd from starting so you could try running pulseaudio -k before starting jack.

AlecB · 2013-05-08 15:28:48

No, when I tried to start qjackctl, I got a unresponsive white window, that should have been qjackctl. I think that dibs is running, because I'm using systemd. I tried killing pulseaudio, but jack still failes.

ooo · 2013-05-09 13:12:40

could you try starting jackd from command line with something like jackd -R -P89 -dalsa -dhw:0 If that doesn't work you should see some errors in output, or if it does work, then its dbus related issue.

you can make sure dbus is running with ps -A |grep dbus.

also dbus needs to be started for your user session as well. If youre using some desktop environment like gnome or kde, this should be done by default.
If you are using custom X session you should put dbus-launch --sh-syntax --exit-with-session <window manager> in your xinitrc

Last edited by ooo (2013-05-09 13:19:52)

AlecB · 2013-05-09 15:26:45

That's odd, when I tried to run

jackd -R -P89 -dalsa -dhw:0

I got

bash: jackd: command not found

Funny...
And yes, dbus is running. I'm using Enlightenment, and it's started on startup.

ooo · 2013-05-09 20:27:18

oh sorry, I forgot jack2-dbus doesn't have jackd binary, so if you could install jack2 package and try with it

AlecB · 2013-05-09 20:51:19

Hmm, I replaced jack2-dbus with jack2, and

jackd -R -P89 -dalsa -dhw:0

Gives me

jackdmp 1.9.9.5
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
Failed to connect to session bus for device reservation Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

jackd: ../dbus/reserve.c:391: rd_acquire: Assertion `0' failed.
Aborted (core dumped)

ooo · 2013-05-12 22:00:15

that looks like it fails to connect to dbus.
could you try if 'dbus-launch jackd -R -P89 -dalsa -dhw:0' works

AlecB · 2013-05-14 00:32:22

I tried running

dbus-launch jackd -R -P89 -dalsa -dhw:0

but I only got

jackdmp 1.9.9.5
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 89
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback

ooo · 2013-05-14 12:57:58

i don't see any errors there.
Is jack still not working?

AlecB · 2013-05-14 16:45:51

Nope, Jack's still not running.

Last edited by AlecB (2013-05-14 18:46:43)

gonX · 2013-05-14 18:52:11

Looks like it's running. Can you interact with it using qjackctl after it has started like above?

AlecB · 2013-05-14 21:11:41

I tried running

dbus-launch jackd -R -P89 -dalsa -dhw:0

in root, and I receive

jackdmp 1.9.9.5
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 89
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.


ATTENTION: The playback device "hw:0" is already in use. The following applications  are using your soundcard(s) so you should  check them and stop them as necessary before  trying to start JACK again:

jackdbus (process ID 16063)

Cannot initialize driver
JackServer::Open failed with -1
Failed to open server

Any idea what it means?

gonX · 2013-05-14 21:37:24

It means your sound card is already in use. If you use Pulseaudio you should use jack2-dbus - then when you start JACK, Pulseaudio will then unlock your soundcard and redirect output to the JACK sink instead.

Alternatively, if you don't want to play around with jack2-dbus (it works like hell for me), try pulseaudio -k then run JACK again

If you don't use Pulseaudio, close all applications which might have grabbed your sound card - mpd is a common one if you use that.

Also your syntax is incorrect. -D means which driver to use (alsa, oss, etc.), -d means what device to use. Nope, your syntax is great.

Last edited by gonX (2013-05-14 22:28:11)

AlecB · 2013-05-14 22:19:30

Thanks for fixing my syntax! I've killed pulseaudio, and I don't have any other application open that should be using my sound card. Do you
know what it might be?

gonX · 2013-05-14 22:27:39

Wow I messed up there haha. It's been so long since I used JACK, but the first -d determines what backend to use, and if you use ALSA, the second -d will determine what device.

These 2 commands will check what processes are locking through OSS and ALSA, respectively:

sudo fuser -v /dev/dsp*
sudo fuser -v /dev/snd/*

AlecB · 2013-05-14 22:36:57

With

sudo fuser -v /dev/dsp*

I get nothing, but with

sudo fuser -v /dev/snd/*

I get

                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  alec        470 F.... enlightenment
                     alec      16063 F.... jackdbus
/dev/snd/pcmC0D0c:   alec      16063 F...m jackdbus
/dev/snd/pcmC0D0p:   alec      16063 F...m jackdbus

gonX · 2013-05-14 22:42:13

jackdbus is already running. Kill it (kill `pidof jackdbus`) and try again

Last edited by gonX (2013-05-14 22:42:36)

AlecB · 2013-05-14 22:45:05

That's odd, I ran

killall jackdbus

but I still get the same message from

sudo fuser -v /dev/snd/*

gonX · 2013-05-14 22:49:17

Try killall -9 jackdbus

Last edited by gonX (2013-05-14 22:49:31)

gonX · 2013-05-14 22:52:35

Also enlightenment seems to be grabbing mixer control of your sound card, but I don't think that should be an issue

Last edited by gonX (2013-05-14 22:52:48)

AlecB · 2013-05-14 23:03:50

Thanks, that did it! Now

fuser -v /dev/snd/*

Only shows

                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  alec        470 F.... enlightenment

ooo · 2013-05-14 23:34:41

when you first tried to launch jackd it failed because it couldn't connect to dbus. adding dbus-launch to the command removed that error. so dbus probably isn't started on your session and obviously you can't control jack over dbus.

replacing 'enlightenment' (or whatever you've got there) with 'dbus-launch --sh-syntax --exit-with-session enlightenment' in your .xinitrc usually helps.

if jack still doesn't work, I suggest using qjackctl to make sure you got it configured properly.

also its better not to start it as root. add your user to audio group to enable realtime priorities

Last edited by ooo (2013-05-14 23:37:26)

AlecB · 2013-05-15 00:15:16

My system refuses to boot when I change that line in .xinitrc. Is there a way to start dbus after I've booted, instead? And when I try to launch qjackctl, I just get a blank window. This just keeps getting weirder and weirder...

ooo · 2013-05-15 00:42:36

can you post your complete .xinitrc?
also are you using any any display managers like entrance or gdm?

it's also possible that qjackctl freezes if it trying to connect to dbus and fails

Arch Linux

#1 2013-05-08 01:22:08

Jack2-dbus Doesn't Start

#2 2013-05-08 11:44:01

Re: Jack2-dbus Doesn't Start

#3 2013-05-08 15:28:48

Re: Jack2-dbus Doesn't Start

#4 2013-05-09 13:12:40

Re: Jack2-dbus Doesn't Start

#5 2013-05-09 15:26:45

Re: Jack2-dbus Doesn't Start

#6 2013-05-09 20:27:18

Re: Jack2-dbus Doesn't Start

#7 2013-05-09 20:51:19

Re: Jack2-dbus Doesn't Start

#8 2013-05-12 22:00:15

Re: Jack2-dbus Doesn't Start

#9 2013-05-14 00:32:22

Re: Jack2-dbus Doesn't Start

#10 2013-05-14 12:57:58

Re: Jack2-dbus Doesn't Start

#11 2013-05-14 16:45:51

Re: Jack2-dbus Doesn't Start

#12 2013-05-14 18:52:11

Re: Jack2-dbus Doesn't Start

#13 2013-05-14 21:11:41

Re: Jack2-dbus Doesn't Start

#14 2013-05-14 21:37:24

Re: Jack2-dbus Doesn't Start

#15 2013-05-14 22:19:30

Re: Jack2-dbus Doesn't Start

#16 2013-05-14 22:27:39

Re: Jack2-dbus Doesn't Start

#17 2013-05-14 22:36:57

Re: Jack2-dbus Doesn't Start

#18 2013-05-14 22:42:13

Re: Jack2-dbus Doesn't Start

#19 2013-05-14 22:45:05

Re: Jack2-dbus Doesn't Start

#20 2013-05-14 22:49:17

Re: Jack2-dbus Doesn't Start

#21 2013-05-14 22:52:35

Re: Jack2-dbus Doesn't Start

#22 2013-05-14 23:03:50

Re: Jack2-dbus Doesn't Start

#23 2013-05-14 23:34:41

Re: Jack2-dbus Doesn't Start

#24 2013-05-15 00:15:16

Re: Jack2-dbus Doesn't Start

#25 2013-05-15 00:42:36

Re: Jack2-dbus Doesn't Start

Board footer