Hendrik Wouters <[EMAIL PROTECTED]> wrote:
So I run the following command on a black Linux console (not X): $ X
-query host :1 . This gives me a second "virtual screen". Actually, this
"virtual screen" is on the same "physical display" (aside from the
virtual screen that is started by kdm automatically). I can switch to
both screens by pressing CTRL-ALT-F7 and CTRL-ALT-F8. On the first
virtual screen, auplay and co. take the current X-server (the computer
who has the screen; you can name it the X-terminal if you want) as the
default nas server, which is very convenient. But on the second virtual
screen, that I started manually with X -query host :1 , nas programs
don't take the X-server as default nas audio server. It looks like all
nas programs are confused about the current x-server on the second
virtual screen?
<end quote>
Okay, I see. So when you run NAS programs on the :1 server, you get no
sound at all?
I think you need to specify the following in one of your login files:
export AUDIOSERVER=unix:0
The thing is, NAS has its own server, distinct from the X server. It
would be nice if X servers had NAS built in, but that is not the case
for most X servers. Instead, a default installation on Debian is going
to start a single NAS server that everyone on the machine is supposed to
use. This is different from what the NAS libraries assume: they assume
that every X server has its own NAS server associated with it.
So in fact, it looks like the NAS libraries (and thus audiooss) *are*
trying to talk to the :1 NAS server... but they need to talk to :0!
Explanations aside, does the AUDIOSERVER command above get sound working
for you on the :1 display?
(I'm CC-ing to the bug tracker, because other people are likely to be
running into the same thing, whatever it turns out to be.)
-Lex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
