From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020827 Description of problem: The problem is with v0.2.28. esdplay correctly plays to a local sound server, but no longer plays to a sound server located on a remote host (such as an X11 terminal). Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Launch "esd -public -tcp -nobeeps -port 16001" on a remote host 2. Go to a different host on the same network 3. Find a WAV file to play (ex. /usr/share/sounds/info.wav) 4. esdplay -s REMOTE_HOST /usr/share/sounds/info.wav Actual Results: At this point, nothing happens. If esdplay is used without the "-s" option, it plays correctly on the local host, of course. Expected Results: The sound should play on the remote terminal host. Additional info: I verified this against EsounD v0.2.27 and that works correctly. I also performed the following experiment: 1. Run "esd -public -tcp -nobeeps -port 16001" on a remote host, using v0.2.28 2. Run 'esdplay' on the other host, using v0.2.27 This works, indicating that the problem is with the client side. The server and libraries on the remote terminal are v0.2.28 and are responding correctly. This bug is relatively serious, since there are large terminal deployments that would be affected by lack of sound on the desktop.
I run esd on a 7.1 box with sound hardware, and clients on a remote 8.0 box run using the ESPEAKER environment variable and work ok. I haven't tested the reverse though, of using esd on 8.0 and having remote clients connect to it. Unfortunately, my only 8.0 boxes currently do not have sound hardware in them to test this. If I get a chance soon, I will test this and report back. The esd remote feature is an extremely cool and very useful thing I stumbled upon not long ago. Painless network audio. Yum yum. Will report back on this after I've had a chance to test.
Moved to http://bugzilla.gnome.org/show_bug.cgi?id=103249