Re: [linux-audio-user] jackd disables client connections

On Fri, 9 Feb 2007 22:06:20 -0500
"Lee Revell" <rlrevell@email-addr-hidden-job.com> wrote:

> On 2/7/07, Mirko Swillus <mechko@email-addr-hidden> wrote:
> > Hej once more,
> > On Tue, Feb 06, 2007 at 12:39:13PM +0100, Mirko Swillus wrote:
> >
> > > I can start jackd by a shell and by qjackctl, but after starting no
> > > client is able to connect. Even giving the jackd-instance a name by the
> > > -n option, clients are not able to connect while specifying that name.
> > > There are also no other clients running that could have the same
> > > client-id as my test-clients (qjackctl itself, meterbridge, adour2).
> >
> > One strange thing came up this morning: Ardour2 (ardour-2.0beta11.1) is able
> > to connect to a jackd instance started by the shell (jackd -dalsa), qjackctl
> > not. I also played around with nearly all options of qjackctl for jackd,
> > without success as well, qjackctl is still not able to connect as a client.
> > I'm glad having adour2 and jackd working, but I do need a tool to
> > do the wiring for the jack-connections though.
> >
> > If nobody subscribed to this list has a clue why qjackctl could not connect
> > to a jackd started by itself, maybe there is some alternative to that tool?
>
> It sounds like you have multiple versions of JACK installed. Are the
> Ubuntu jackd and libjack* package installed as well as your
> self-compiled one?
>
> Lee

This is *exactly* the problem I had a while ago, deleting one version
cured the problem.

-- 
Will J G