Please describe the problem:
Using the PulseAudio "esd" drop-in replacement for the Enlightenment esd sound server results in gnome-session reporting when ending a session that it is unable to kill esd (ie: "Failed to kill esd (pid nnnn)").  What happens is when gnome-session execs "esd" it is exec'ing a soft-link to PulseAudio's script "esdcompat".  PulseAudio's esdcompat script then actually execs the binary pulseaudio executable; hence, pulseaudio is actually the name that is recognized as the forked sound daemon.  When gnome-session ends it appears that it only looks for esd as the sound daemon to kill; however, it should be more generic and more flexible to allow the choice of different sound daemons (such as pulseaudio).

It is uncertain whether there are any other side-effects as a result of gnome-session "failing to kill esd"... for example, I am not sure if the result code of this event is detected and may cause other clean ups not to occur such as saving the actual session.

Steps to reproduce:
1. Use the latest Fedora 8 distribution
2. Make sure that GNOME's default esd sound server is not installed or removed 
3. Install and use the pulseaudio-esound-compat rpm package instead
4. Enable the sound server in the GNOME sound setup
5. Log in and out of a GNOME session as an ordinary user.
6. Using a non-graphical or console login check the .xsession-errors file of that ordinary user to see the "Failed to kill esd" message.


Actual results:
GNOME's system sounds are available during the gnome-session once the PulseAudio daemon has started up in place of the Enlightenment sound daemon.  It should also be noted that the GDM, however, is unable to play its system sounds using PulaseAudio this way since the daemon has not been started up as a global service.  Also it takes a while for the the daemon to start up; hence, any sound request at login may be missed depending on system load.  Other PulseAudio users are lamenting this fact as well and are probably asking for a global service version of the PulseAudio sound daemon.

In the case of gnome-session, it would be proper for it to not be tied to just the "esd" sound server alone and should allow further options to indicate other sound server choices such as PulseAudio.

Expected results:
No reporting of failing to kill the sound server and more flexible options of specifying the sound server to be used for GNOME system sounds.

Does this happen every time?
Yes

Other information:
If you need anything else please do not hesitate to ask me.