Re: esound and alsa not compatible?

["H. S." <greatexcalibur@yahoo.com>]

Apparently, _Thomas Hood_, on 24/10/04 15:56,typed:
> On Sun, 24 Oct 2004 21:50:07 +0200, H. S. wrote:
>
> > I could do that. But how does that relate to Alsa? If I install esound, 
> > can I just uninstall Alsa altogether?
>
>
>
> If you use ALSA and esound then you should install libesd-alsa0 instead
> of libesd0.

I already have libesd-alsa0 installed and removed libesd0 (which was 
'rc' and not 'ii' in dpkg info):

~$ dpkg -l libesd*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: 
uppercase=bad)
||/ Name                       Version                    Description
+++-==========================-==========================-====================================================================
ii  libesd-alsa0               0.2.35-2                   Enlightened 
Sound Daemon (ALSA) - Shared libraries
un  libesd-alsa0-dev           <none>                     (no 
description available)
un  libesd-dev                 <none>                     (no 
description available)
pn  libesd0                    <none>                     (no 
description available)
pn  libesd0-dev                <none>                     (no 
description available)


Still the behaviour is the same. The problem is that when the first user 
to use esd logs out .esd in /tmp is not removed:
~$ ls /tmp/.esd/socket -l
srwxrwxrwx  1 <user> <user> 0 2004-10-24 20:00 /tmp/.esd/socket

is still there when the second user logs in to gdm.

->HS