I have noticed this behavior on occasion as well. It has caused far too
many "sudo killall -9 pulseaudio" calls!
On my system I always know because it warns about being unable to access
my output device and then fails to run.
Which distrib's are you packaging for again?
Matt
CJ van den Berg wrote:
On Thu, Feb 21, 2008 at 12:18:46AM +0000, Colin Guthrie wrote:
Anyway, to cut a long story short, I eventually found that it was
actually libesound that was starting this process. If you run an
application as root (e.g. firestarter - a gtk firewall thingy) that used
libesound it would go through some code that checked for the existence
of /etc/esd.conf. If this file did not exist, the bahaviour is such that
the library will try to *autospawn "esd" by default*. This is in
contrast to the default esd.conf shipped with esound which has
auto_spawn=0 specified in it. Go figure!
So to fix this problem I simply ship an /etc/esd.conf with the
pulseaudio-esound-compat package. The alternative is to patch libesound
to not do the auto spawn by default thing but this seemed cleaner.
I hope this helps someone not go insane as I nearly did :)
Very good-to-know info. Thanks for saving us from taking the same
horrible journey! :-D
------------------------------------------------------------------------
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
