Mike, The pulseaudio daemon always runs where the soundcard is - in the case of LTSP, that means on the thin client. *No pulseaudio daemon need/should run on the server*
The apps on your application servers are all pulseaudio clients. In order for them to know the IP address of the pulseaudio daemon, an environment variable PULSE_SERVER is set upon login. An example would be: PULSE_SERVER=tcp:192.168.2.29:4713 , where 192.168.2.29 is the thin client IP in this case. This variable is usually set by LDM upon login. If you are not using LDM, you must set this variable using your own means (a server-side Xsession.d script, perhaps?) Also, if the thin client is not on the same subnet as the application server, there must be a route from the application server TO the thin client. That is, the pulseaudio clients cannot be blocked by a NAT firewall or the like. In Gnome, you should also ensure that either gstreamer is set to use pulseaudio as its output, or (preferred) that alsa is set to redirect its output to pulse (which is done by presenting alsa with a pulseaudio virtual soundcard device in asound.conf) Hope this helps, -Gadi ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _____________________________________________________________________ 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
