[Fwd: Sound broke on my system after 1.0.40]



Additional info:
- warning dialog on gnome startup saying "unable to connect to sound
daemon, restart .. .etc".
- esd is running

[weberd@dweber weberd]$ ps aux | grep esd
weberd    1068  0.0  0.3  1768  884 ?        S    Oct02   0:13 esd
-terminate -n

- fuser reports no connection to /dev/dsp
- sounds work correctly
- sound monitor reports no connection to esd

RPM's installed:
esound-devel-0.2.14-1
rhsound-1.8-1
esound-0.2.14-1
sound-monitor-0.7.0-2

esd.conf
[weberd@dweber weberd]$ cat /etc/esd.conf
[esd]
auto_spawn=1
spawn_options=-terminate -nobeeps -as 2
spawn_wait_ms=100

any more information available on request

daniel


Elliot Lee wrote:

> On Sat, 2 Oct 1999, Dan Hensley wrote:
>
> > > On Sat, 2 Oct 1999, Dan Hensley wrote:
> > >
> > > >     I recently installed Gnome-1.0.4x on my system, and ever since I
> > > > restarted sound has been broken.  It worked fine until then.  What
> > > > happens is I can start esd, get the tones saying it starts up.  Then I
> > > > do esdctl unlock.  Right after that I do an esdcat, and I get opening
> > > > socket, format = 0x00001021 at 44100 Hz /dev/dsp: Device or resource
> > > > busy
> > >
> > > What does '/usr/sbin/fuser -uv /dev/dsp' say?
> >
> > [root@danlinux /root]# fuser -uv /dev/dsp
> >
> >                      USER        PID ACCESS COMMAND
> > /dev/dsp             root      20482 f....  esd
> >
> > What does this mean?
>
> It looks like things are not connecting to esd properly. If I can figure
> out how to reproduce the problem, I'll have a look at it.
>

I''m having esd problems on my system as well after upgrading to 1.0.50pre
(including gnome-libs 1.0.51)





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