On Thu, Feb 21, 2008 at 12:18:46AM +, 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
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
On Thu, Feb 21, 2008 at 08:16:12AM -0800, Matthew Patterson wrote:
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
CJ van den Berg wrote:
On Thu, Feb 21, 2008 at 08:16:12AM -0800, Matthew Patterson wrote:
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
Hi,
This is a little story that I've only just recently fully appreciated
As with many distro's I've repackaged esound such that the actual binary
is distributed separately and as such pulse can be installed with it's
/usr/bin/esdcompat script symlinked to /usr/bin/esd.
Anyway, while doing
