[pulseaudio-tickets] [PulseAudio] #587: Esound usability/compatibility broken on AMD64 in pulseaudio 0.9.15

[PulseAudio]

#587: Esound usability/compatibility broken on AMD64 in pulseaudio 0.9.15
----------------------+-----------------------------------------------------
  Reporter:  PhobosK  |       Owner:  lennart        
      Type:  defect   |      Status:  new            
 Milestone:           |   Component:  module-esound-*
Resolution:           |    Keywords:                 
----------------------+-----------------------------------------------------

Comment(by PhobosK):

 Well...[[BR]]
 The output of PA i have given above, is the output that changes
 '''while''' esdplay is run. [[BR]]
 I guess the
 {{{
 I: alsa-sink.c: Starting playback.
 }}}
 means esdplay has connected to PA?[[BR]]
 For a very short period of time esdplay displays as a client in the
 pavucontrol (the playback section). The wav file that is played is long
 enough and i tried a lot of other sound files.[[BR]]

 About the /tmp/.esd and /tmp/.esd-{$UID} issue - gentoo compilation uses
 the first one, and pure source uses the second one. The result of both
 compilations is the same - no sound and esdplay connecting to PA.[[BR]]

 esdplay opens the right socket and gives no errors anyway. I had that
 problem on Ubuntu Intrepid long ago on another PC but after the upgrade to
 Jaunty it disappeared, so i guess it is something from the code.
 I have tried changing a lot of the options in the config of PA with no
 success.
 What else can I do so you can pinpoint the problem?

 And btw the problem is with '''ANY''' esd client.... and it is on
 '''AMD64'''... and the problem is gone if native esound server is used for
 the clients (of course PA is not running at that time)....

-- 
Ticket URL: <http://pulseaudio.org/ticket/587#comment:4>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server