Re: [LAD] [Jack-Devel] more jack/qjackctl madness

PrevNext  Index
DateMon, 18 May 2009 11:10:58 +0300
From Nedko Arnaudov <[hidden] at arnaudov dot name>
ToFons Adriaensen <[hidden] at kokkinizita dot net>
CcLinux Audio Developers <[hidden] at lists dot linuxaudio dot org>, JACK Developers <[hidden] at jackaudio dot org>
In-Reply-ToFons Adriaensen Re: [LAD] [Jack-Devel] more jack/qjackctl madness
Follow-Upalex stone Re: [LAD] [Jack-Devel] more jack/qjackctl madness
Fons Adriaensen <[hidden]> writes:

> On Sun, May 17, 2009 at 09:36:12AM +0200, Stéphane Letz wrote:
>
>> I really appreciate your feedback...,  but AFAICS Qjackctl is *absolutely* 
>> not using the DBUS layer!
>
> Then please tell what this is:  (ps -ef output)
>
> fons      2444     1  0 10:43 ?        00:00:00 /usr/bin/jackdbus auto
>
> Killing this makes qjackctl behave normally again,
> and allows me to start the server configured in it
> Setup window instead of getting a different one.

Presence of jackbus process does not mean that jack server is
started. It means that jack server may or may not be started. jackdbus
service is there to allow in future creation of multiple jack servers.

the easiest way to check whether jack server is started by jackdbus
service is:

jack_control status

-- 
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
PrevNext  Index

1242634354.29829_0.ltw:2,a <87fxf2kezx.fsf at usbix dot spacelabs dot org>