You are not logged in.
Pages: 1
Hello everyone,
For the sake of reference, I will start by saying I have installed the following packages in order to try and get jack to work.
jackdbus
python2-dbus
qjackctl
pulseaudio-jack
And I've updated every package ~3 hours ago. Trying to start jack the following ways:
dbus-launch jack_control start
jack_control start
Gives me the same output:
DBus exception: org.jackaudio.Error.Generic: Failed to open server
(Exact same for both)
Trying to start through method one with a sudo works, but I'd rather not use jack like that, since literally every guide out there seems to assume you've started it as root.
Also, trying to start jack_control does actually live a zombie process in the background:
3199 0.0 0.0 139820 7532 ? Ss 20:43 0:00 /usr/bin/jackdbus auto
(These simply accumulate each time I run the command, getting rid of them does not make the command work)
I've followed the instruction under this section:
https://wiki.archlinux.org/index.php/Pu … rough_JACK
Under the "The new new way" heading.
The only thing I might be doing wrong is trying to start jack after boot. Might that be a problem ? And if so, how would one start jack at boot ? Currently I start my X server using the following lines in .zprofile:
if [ -z "$DISPLAY" ] && [ -n "$XDG_VTNR" ] && [ "$XDG_VTNR" -eq 1 ]; then
exec startx
fi
and then I execute most logic in my ~/.xinitrc
however putting jack_control start in my .xinitrc leaves me hanging at boot for minute, without any end in sight, unable to even switch to a different tty or press some esoteric key combination to quit.
dmesg also doesn't help much, the only only logs present there are the "usual" ones related to vga, bluetooth, internet interfaces.... etc
How can I debug this problem ? Is there a package that might be causing this (I double checked but I don't seem to have anything jack 1 or jack 2 specific installed, no jackd in sight) ? Is there an easier solution to start jack that I'm not seeing ?
Edit:
Apparenly there is a default configuration ~/.config/jack/config.xml
That comes with one of the packages and nobody in the wiki cared to mention... which is used as the default when starting jack and on my machine its not quite suitable (as in, not at all)...
I mean, now its working, but it would be nice if this were in the wiki... seeing as it was actually very hard to pin point where random jack settings came from....
Last edited by TheHadoopBandwagon (2017-04-05 22:47:52)
Offline
Is your user in the audio group?
You may also try to install jack2 instead and test with jackd first. No experience with the dbus variant so no idea where to look for more messages.
P.S. Apparently the jack2 package provides the dbus interaction funtionality as well. I wonder why there is a dbus-only build/split package.
Last edited by tom.ty89 (2017-04-06 02:37:01)
Offline
As I understand from the wiki jack2-dbus is similar to jack2 but without the jackd, since that is now redundant.
Either way, for me, both jack2 dbus and jack2 work similarly now, as in:
-> They start
-> They seem to work on the input side(I can can connect a midi/soundcard out to ardour or qsynth)
-> They don't deliver any sound (connection qsynth or ardour to the system playback does nothing ![]()
Any further help would be apperciated
Also, yes, my user is in the audio group (and I don't have a realtime group)... but I believe the audio group is there just to grant user-ran application some specific privilages in order to ignore some of the values in /etc/security/limits.conf. Or am I mistaken ?
Last edited by TheHadoopBandwagon (2017-04-06 07:32:26)
Offline
Pages: 1