[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sound not working after computer upgrade



On Sat, Oct 30, 2010 at 08:22:50AM -0400, Rodney D. Myers wrote:
> On 10/30/10 7:19 AM, Camaleón wrote:
> > On Fri, 29 Oct 2010 18:29:57 -0400, Rodney D. Myers wrote:
> > 
> >> > On 10/29/10 6:05 PM, Camaleón wrote:
> >>> >> Do you have ESD enabled? If so, try to disable.
> >>> >> 
> >>> >> Also, recheck your sound device permissions:
> >>> >> 
> >>> >> sm01@stt008:~$ ls -l /dev/snd
> >>> >> total 0
> >>> >> crw-rw---- 1 root audio 116,  0 oct 29 07:42 controlC0
> >>> >> crw-rw---- 1 root audio 116, 24 oct 29 07:42 pcmC0D0c
> >>> >> crw-rw---- 1 root audio 116, 16 oct 29 23:56 pcmC0D0p
> >>> >> crw-rw---- 1 root audio 116, 28 oct 29 07:42 pcmC0D4c
> >>> >> crw-rw---- 1 root audio 116,  1 oct 29 07:42 seq
> >>> >> crw-rw---- 1 root audio 116, 33 oct 29 07:42 timer
> >>> >> 
> >> > 
> >> > My permissions match yours.
> >> > 
> >> > esd claims to be running;
> >> > 
> >> > esd
> >> > esd: Esound sound daemon already running or stale UNIX socket
> >> > /tmp/.esd/socket
> >> > This socket already exists indicating esd is already running. Exiting...
> > Hum... what happens if you stop ESD daemon?
> > 
> > Another thing you can try is playing the file with an external app, like 
> > totem from command line, i.e., "totem /usr/share/sounds/purple/send.wav" 
> > and see what happens :-?
> > 
> > Greetings,
> 
> That would do it.
> 
> Now, do I need ESD to run the system? Or do I need to try and figure out
> why ESD is doing this?
> 
ESD has a lock file of sorts.  It's in the /tmp/.esd directory.  You can
try removing that entire directory (it will be recreated when the next
user logs in).  It's possible that due to a bug, ESD is still locked to
another user.

-Rob


Reply to: