Jack2-dbus Doesn't Start

AlecB · 2013-05-15 01:25:35

Here's my xinitrc:

                       File: .xinitrc                                                                                                

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice

exec enlightenment_start

compton --config ~/.compton.conf -b

/usr/bin/xscreensaver -no-splash &

Last edited by AlecB (2013-05-15 01:26:36)

ooo · 2013-05-15 04:28:41

changing this

exec enlightenment_start

to this

dbus-launch --sh-syntax --exit-with-session enlightenment_start

should solve dbus-related issues.

AlecB · 2013-05-15 20:48:01

I changed that line in xinitrc, and it boots up fine, but

jack_control start

still gives

--- start
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.

Qjackctl still just gives three blank windows.

ooo · 2013-05-15 21:04:11

ugh...

how about if you start it with jackd? does that work?

also try removing config files for qjackctl in ~/.config/rncbc.org/QjackCtl.conf and ~/.jackdrc if it exists

AlecB · 2013-05-16 05:53:54

I removed those config files, but I can't use jackd to start it because I'm using jack2-dbus. I just tried qjackctl in root, and it works, but when I try to start it, it fails. Here are the contents of my message window:

22:52:32.645 Patchbay deactivated.
22:52:32.646 Statistics reset.
22:52:32.647 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
22:52:32.653 ALSA connection graph change.
22:52:34.085 JACK is starting...
22:52:34.085 jackd -dalsa -dhw:0 -r48000 -p1024 -n2
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
22:52:34.094 Could not start JACK. Sorry.
22:52:37.483 JACK was stopped with exit status=255.

Last edited by AlecB (2013-05-16 05:54:12)

ooo · 2013-05-16 13:45:23

those config files belong to qjackctl so I thought if you removed them you could be able to start qjackctl again as user.

also you could've just used the jack2 package instead of jack2-dbus, since it has both the jackd binary and jack_control etc. used to control it via dbus. only difference afaik between these two packages is that jack2-dbus doesn't have the jackd binary.

I did some googling with the error you're getting, and some people were having similar issues because of pulseaudio. so if you're still using it, please try killing it again with pulseaudio -k (or killall -9 pulseaudio if that doesn't work) and see if that helps.

if jack starts working after that. there's a couple of methods using pulseaudio with jack. I think they are mentioned in arch wiki.

I'm starting to get out of ideas if that doesn't work...

AlecB · 2013-05-16 14:58:04

I rebooted, killed pulseaudio and started qjackctl. Now I get the normal window but when I go to start it, I get :

07:54:09.015 Patchbay deactivated.
07:54:09.017 Statistics reset.
07:54:09.031 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
07:54:09.049 ALSA connection graph change.
07:54:11.818 JACK is starting...
07:54:11.818 jackd -dalsa -dhw:0 -r48000 -p1024 -n2
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
07:54:11.822 Could not start JACK. Sorry.
07:54:13.477 JACK was stopped with exit status=255.

And a message box pops up saying " Could not start JACK. Sorry."

ooo · 2013-05-18 14:28:08

good to hear qjackctl at least is working now

unfortunately i can't help you very much. most likely there's something with your jack configuration.

make sure you're using the right audi interface. hw:o is usually right but this depends on your setup.

try using different sample rate, in some cases your soundcard may work with only one specific sample rate. I know there's a way to see what rates are supported but i cant figure out how did you do it. alsa's homepage should have pages of all soundcard drivers that might give more info.

you could also try with different frames/period and periods/buffer values.

also make sure that your user is in 'audio' group

if you cant get jack to work with alsa you could also try to use pulseaudio for its output driver, although I have zero experience with it so I can't really tell how well it works.

AlecB · 2013-05-18 15:47:00

Thanks for all your help, I'll try your suggestions.

AlecB · 2013-05-25 00:13:20

Arggh, I've discovered some other things, but the topic I started was closed.

Any way, to recap, here's a list of everything that won't work:

When I try to start jack2-dbus with

jack_control start

I get

--- start
ERROR:dbus.proxies:Introspect error on :1.8:/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.
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.

When I try to start jack2-dbus with qjackctl, I get

16:15:30.393 Could not start JACK. Sorry.
16:15:30.401 JACK was stopped with exit status=255.

When I try to start jack2, (NOT dbus), with

jack_control start

I get exactly what I got before with jack2-dbus.
When I try to start jack2 with qjackctl, I get

16:24:50.948 Patchbay deactivated.
16:24:50.950 Statistics reset.
16:24:50.951 ALSA connection change.
Cannot connect to server socket err = Connection refused
Cannot connect to server request channel
jack server is not running or cannot be started
16:24:50.957 ALSA connection graph change.
16:24:52.854 JACK is starting...
16:24:52.854 /usr/bin/jackd -t5000 -dalsa -dhw:0 -r48000 -p1024 -n2
Cannot connect to server socket err = Connection refused
Cannot connect to server request channel
jack server is not running or cannot be started
16:24:52.861 JACK was started with PID=13731.
no message buffer overruns
no message buffer overruns
no message buffer overruns
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
JACK server starting in realtime mode with priority 10
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
16:24:59.963 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info.
16:24:59.973 JACK is stopping...
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
Cannot read socket fd = 15 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open qjackctl client
Unknown request 4294967295
CheckSize error size = 0 Size() = 12
CheckRead error
Jack main caught signal 15

sudo fuser -v /dev/snd/*

Gives me

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

Any ideas?

Arch Linux

#26 2013-05-15 01:25:35

Re: Jack2-dbus Doesn't Start

#27 2013-05-15 04:28:41

Re: Jack2-dbus Doesn't Start

#28 2013-05-15 20:48:01

Re: Jack2-dbus Doesn't Start

#29 2013-05-15 21:04:11

Re: Jack2-dbus Doesn't Start

#30 2013-05-16 05:53:54

Re: Jack2-dbus Doesn't Start

#31 2013-05-16 13:45:23

Re: Jack2-dbus Doesn't Start

#32 2013-05-16 14:58:04

Re: Jack2-dbus Doesn't Start

#33 2013-05-18 14:28:08

Re: Jack2-dbus Doesn't Start

#34 2013-05-18 15:47:00

Re: Jack2-dbus Doesn't Start

#35 2013-05-25 00:13:20

Re: Jack2-dbus Doesn't Start

Board footer