Thank you Denis for the answer, I was starting to give up :-)
If I understand you right, you are refering to the script in the LTSP
directory (in my case /opt/ltsp/i386/etc/rc.sound). When I looked at
that file, I found (line 66):
export ESD_SPAWN_OPTIONS="-public"
I did try adding "-public" in the config file for my the server, but
that did not help any. That got be wondering if a setting on the
servers config file was messing me up. Currently I have esd being
launched (at the server) with:
/etc/esound/esd.conf
[esd]
auto_spawn=0
# tried with '-public' but did not help LTSP clients
spawn_options=-terminate -nobeeps -as 5
spawn_wait_ms=100
# default options are used in spawned and non-spawned mode
default_options=
Looking through the 'man esd' I am wondering if I should have
auto_spawn=1 or maybe -tcp as one of the options. I know I could just
try it out and see, but I am wondering if anyone might know --
Even if one or both of the options work, would I be opening up some
other problem on the server?(the "server" is also my work station)
On Wed, 19 Apr 2006 01:20:30 +0200
Denis Cardon <[EMAIL PROTECTED]> wrote:
> Hi gentgeen,
>
> > I have a problem with sound after the first login. On 2 of my 3
> > clients, the first login ALWAYS has sound. Sound works great for
> > any and all apps that I have thrown at it. But after that person
> > logs out, the only way to get sound again is to reboot the client.
>
> esd has somekind of authentication build in based on cookies, and when
> the second person log in, the esound server on the thin client refuse
> the connexion from the sound applications. The only way I found to
> have it working fine all the time is to add the "-public" flag in the
> rc.sound script (look for the line launching esd). It is probably not
> the most elegant way, but it certainly works.
>
> Cheers,
>
> Denis
>
>
> >
> > Server is Debian Etch (testing).
> > All users are using "icesound-experimental -i ESD" for the desktop.
> > Using ESD to "push" sound to the clients
> > Happens to all users, no matter who or what order they log in.
> >
> > Client one has an onboard Crystal CS4235 built-in Sound Blaster Pro,
> > MPC-3, MPU-401 compatible Audio Enhanced Stereo full duplex
> > operation and lts.conf has: (ignore wraping)
> >
> > SMODULE_01 = "cs4232 io=0x534 irq=5 dma=1 dma2=3 mpuio=0x330
> > mpuirq=9 synthio=0x0220 isapnp=0"
> >
> >
> > Client two has an onboard ESS Solo-1 and lts.conf has:
> > SMODULE_01 = "esssolo1"
> > SMODULE_02 = "snd-seq-device"
> > SMODULE_03 = "snd-seq-midi"
> > SMODULE_04 = "snd-mixer-oss"
> >
> > My third client, works just fine all the time. I has an old ISA
> > soundblaster add-on card, and lts.conf of:
> > SMODULE_01 = "sb irq=5 io=0x220 dma=1"
> >
> >
> > Since it works for Client #3 but not for the others, I assume the
> > problem is the lts.conf for those two or those chipsets do not play
> > well with linux/ltsp. I have googled like crazy, but as you can
> > imagine, LTSP + SOUND + PROBLEMS show up a lot of false positives
> > (at least for my case)
> >
> >
> > Does anyone have any thought or pointers?
--
*****************************************************************
Associate yourself with men of good quality if you esteem
your own reputation; for 'tis better to be alone then in bad
company. - George Washington, Rules of Civility
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
