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

Peter Verbaan verbaan.peter at gmail.com
Sun Feb 22 18:29:54 UTC 2009

Package: libesd-alsa0
Followup-For: Bug #516081


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 .

Hope this helps.


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.28-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libesd-alsa0 depends on:
ii  esound-common                 0.2.41-2   Enlightened Sound Daemon - Common 
ii  libasound2                    1.0.16-2   ALSA library
ii  libaudiofile0                 0.2.6-7    Open-source version of SGI's audio
ii  libc6                         2.9-3      GNU C Library: Shared libraries

Versions of packages libesd-alsa0 recommends:
pn  esound-clients                <none>     (no description available)

Versions of packages libesd-alsa0 suggests:
ii  pulseaudio-esound-compat [eso 0.9.10-3   PulseAudio ESD compatibility layer

-- no debconf information

More information about the pkg-gnome-maintainers mailing list