Re: [a-devel] AGNULA/DeMuDi 1.1.1 and 2.6.x kernel
i meant using as A first, shutting down jack, logging out,
and then running jack as B, no client can connect at all.
running as A again will work.
i can reproduce the bug, but i don't find any relevant messages. the
clients just can see the server it seems. launching 'jack -v -d alsa'
gives something like this :
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
2143 waiting for signals
but jack clients will complain about no server found. not sure what is the
best way to track the problem from here.
piem
On Thu, Jun 17, 2004 at 06:33:54PM -0500, Jack O'Quin wrote:
> Paul Brossier <piem-lists@altern.org> writes:
>
> > i had some strange behaviors with 2.6.6 too, including freeze and X
> > crashes, and also some of them probably related to realtime. for instance,
> > i could launch jack perfectly as userA, but when userB was then trying, he
> > could not: only the first user could actually access jack (this was with an
> > rme9652 and 2.6.6)
>
> This is a JACK restriction, not realtime-lsm. All clients must run
> the same user ID as the server.
> --
> joq
>
>
> --
> To UNSUBSCRIBE, email to debian-multimedia-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: