30 Sep
2014
30 Sep
'14
1:23 p.m.
Dear LAU
Whenever I'm starting to get xruns, I do a quick ps aux|grep jack and
sure enough, in place of the usual
(...) /usr/bin/jackd -dalsa -dhw:XStation,0 -r48000 -p512 -n3 -Xseq
I get a nasty
(...) /usr/bin/jackdbus auto
I' suspecting pulseaudio to launch it (I use 3.13.0-36-lowlatency
#63-Ubuntu SMP PREEMPT) so I edited
/etc/pulse/default.pa
To comment out those lines
### Automatically connect sink and source if JACK server is present
# .ifexists module-jackdbus-detect.so
# .nofail
# load-module module-jackdbus-detect channels=2
# .fail
# .endif
But nope, at some point, jackdbus rears its ugly head.
Then I have to reboot :[ because just killing -9 it prevents the jack
server to start anew.
Questions
- What is wrong with jackdbus ?
- How can I prevent it from starting ?
Thanks
--
Phil CM
30 Sep
30 Sep
1:57 p.m.
Tue, 30 Sep 2014 12:23:21 +0100, Phil CM wrote :
Questions
- What is wrong with jackdbus ?
- How can I prevent it from starting ?
Delete or backup :
/usr/share/dbus-1/services/org.jackaudio.service
Or rename it to something else like :
/usr/share/dbus-1/services/org.jackaudio.service.orig
Or comment the line :
Exec=/usr/bin/jackdbus auto
Thanks
You're welcome.
--
Phil CM
--
Marc
3:27 p.m.
On Tue, 30 Sep 2014, Phil CM wrote:
Dear LAU
Whenever I'm starting to get xruns, I do a quick ps aux|grep jack and sure
enough, in place of the usual
(...) /usr/bin/jackd -dalsa -dhw:XStation,0 -r48000 -p512 -n3 -Xseq
I get a nasty
(...) /usr/bin/jackdbus auto
I' suspecting pulseaudio to launch it (I use 3.13.0-36-lowlatency #63-Ubuntu
SMP PREEMPT) so I edited
/etc/pulse/default.pa
To comment out those lines
### Automatically connect sink and source if JACK server is present
# .ifexists module-jackdbus-detect.so
# .nofail
# load-module module-jackdbus-detect channels=2
# .fail
# .endif
But nope, at some point, jackdbus rears its ugly head.
Then I have to reboot :[ because just killing -9 it prevents the jack server
to start anew.
Questions
- What is wrong with jackdbus ?
- How can I prevent it from starting ?
If you run qjackctl, it may start jackdbus. In fact anything that tries to
see if jackdbus is alive will start jackdbus. This does not mean it is
active.
The problem is with the debian (and so ubuntu) jack2 package that installs
both jackd and jackdbus. There should only be one or the other on a
system. I would suggest that:
sudo chmod -x /usr/bin/jackdbus
will fix your problem. Then, if you use qjackctl, unselect the Dbus option
on the last setup page.
Personally, I would use jackdbus instead if I am running dbus anyway. On
my systems I have chmod -x jackd instead. The best thing is to run the one
you feel most comfortable with.
The problem with splitting jack2 into two packages probably has something
to do with having to redo the depends for all the other packages using
jack2. Because I happen to use jackdbus, my opinion is that /usr/bin/jackd
should be a script that takes the normal jackd command line and uses them
to run jack_control to start jackdbus. However, I am sure that lots of
people would hate that idea and I am not going to make such a script
either.... I am not trying to start a discusion on it :)
--
Len Ovens
www.ovenwerks.net
1 Oct
1 Oct
1:20 a.m.
Tue, 30 Sep 2014 06:26:49 -0700 (PDT), Len Ovens wrote :
Removing the execution bit on the jackdbus binary (using chmod -x)
would not prevent D-bus from trying to start it, generating useless
activity on the system, maybe resulting in errors and growing log
files. I think it'd better to disable the D-bus jackaudio service.
--
Marc
Questions
- What is wrong with jackdbus ?
- How can I prevent it from starting ?
If you run qjackctl, it may start jackdbus. In fact anything that
tries to see if jackdbus is alive will start jackdbus. This does not
mean it is active.
The problem is with the debian (and so ubuntu) jack2 package that
installs both jackd and jackdbus. There should only be one or the
other on a system. I would suggest that:
sudo chmod -x /usr/bin/jackdbus
will fix your problem. Then, if you use qjackctl, unselect the Dbus
option on the last setup page.
Personally, I would use jackdbus instead if I am running dbus anyway.
On my systems I have chmod -x jackd instead. The best thing is to run
the one you feel most comfortable with.
1:58 a.m.
On Tue, 30 Sep 2014, Marc Lavallée wrote:
Tue, 30 Sep 2014 06:26:49 -0700 (PDT), Len Ovens wrote
:
> The problem is with the debian (and so ubuntu) jack2 package that
> installs both jackd and jackdbus. There should only be one or the
> other on a system. I would suggest that:
> sudo chmod -x /usr/bin/jackdbus
Removing the execution bit on the jackdbus binary
(using chmod -x)
would not prevent D-bus from trying to start it, generating useless
activity on the system, maybe resulting in errors and growing log
files. I think it'd better to disable the D-bus jackaudio service.
Having seen your reply, I agree.
--
Len Ovens
www.ovenwerks.net
3708
days inactive
3708
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
Len Ovens -
Marc Lavallée -
Phil CM