Re: [Fwd: Sound broke on my system after 1.0.40]

[Elliot Lee <sopwith redhat com>]

On Tue, 5 Oct 1999, Dan Hensley wrote:

> esd is still broken on my system.  I wasn't using sound monitor
> before, but I tried the new version just in case it could shed some
> light (I'm grasping now, because I can't figure it out).  I've
> compiled everything from source.  The next time I started up after
> installing the main gnome 1.0.4x stuff, esd starts, and I hear the
> tones, but after that everything reports /dev/dsp as busy, no matter
> what.  fuser states that esd has that device, and it's locked bythe
> user who started esd.  I have no idea why it thinks the device is
> busy. I even tried reverting back to older audiofile and esound, but
> it's still broken.  I started looking at esd in a debugger, but I
> still can't see what's wrong.  If any one has _any_ ideas of what
> could have broken this, I'm all ears.

If you do:

	killall esd
	esd &
	esdplay foo.wav

Does it work?

Just a wild guess that maybe it's running as another user. I can't
reproduce the problem, so can't fix it :(
-- Elliot					http://developer.gnome.org/
The first thing a programmer needs to admit is that any program is by far
more complex than his own mind. Thats why he partitions it into neat
pieces and avoids complexity.