Bug#516081: libesd-alsa: ESD socket created in the wrong location

[Julien Valroff]

Le mercredi 25 mars 2009 à 19:34 +0100, Peter Verbaan a écrit :
> Package: libesd-alsa0
> Version: 0.2.41-2
> Severity: normal
> 
> Hi,
> 
> On Wed, Mar 25, 2009 at 18:50h (+0100), Julien Valroff wrote:
> > Le lundi 23 mars 2009 à 18:43 +0100, Josselin Mouette a écrit :
> > > reassign 516081 pulseaudio
> > > thanks
> > > 
> > > Le dimanche 22 février 2009 à 19:29 +0100, Peter Verbaan a écrit :
> > > > Package: libesd-alsa0
> > > > Followup-For: Bug #516081
> > > > 
> > > > Hi,
> > > > 
> > > > This looks similar to ticket 121 in the PulseAudio tracker
> > > > (http://www.pulseaudio.org/ticket/121 ).
> > > > Indeed, with version 2.41-2 of libesd-alsa0,
> > > > the socket is created in /tmp/.esd-`id -u`,
> > > > while in version 2.36-3 the socket is created in /tmp/.esd .
> > > 
> > > According to the discussion in this ticket, pulseaudio needs to be
> > > changed to use /tmp/.esd-`id -u` instead of /tmp/.esd, then.
> > 
> > I have re-assigned this bug to libesd-alsa0 as the problem does not
> > occur with pulseaudio but with plain esound.
> > 
> > All sounds work BUT the GNOME system sounds.
> > 
> > I guess Peter wanted to point out that this could be a problem of
> > incorrect path to the socket, maybe accessed directly by another GNOME
> > component?
> 
> Well, I was/am running pulseaudio, and upgrading from pulseaudio 0.9.10-3 to version 0.9.14-2 solved the problem for me.
> So I guess yours is a different problem.
> What socket does esd use?

/tmp/.esd-1000/socket

There is no other socket in /tmp
As said, only the system sounds do not work (actually, login sound does)

Cheers,
Julien