Glitch-Free PulseAudio in Rawhide

Kevin Kofler kevin.kofler at chello.at
Tue May 20 05:47:35 UTC 2008


Lennart Poettering <mzerqung <at> 0pointer.de> writes:
> Also, if you claim that I neglect longstanding important bugs, then
> please be more specific and tell me exactly the bug numbers.

There's this one:
https://bugzilla.redhat.com/show_bug.cgi?id=438284
"Sometimes, PulseAudio fails to start"
It might actually be a symptom of several completely different bugs. What I'm 
seeing in KDE is that sometimes, for no apparent reason, no PA is running, 
starting it with pulseaudio -D just starts it. But that only happens sometimes. 
I know this is not very useful as a bug report, I'll have to check the logs 
more carefully to see if I can figure out what happens: maybe PA starts up and 
then kills itself due to CPU overload? I'll let you know once I figure out 
more.

Then there's this weird issue:
https://bugzilla.redhat.com/show_bug.cgi?id=361891
The setup aRts->ALSA->alsa-plugins-pulseaudio->PA usually works (with very low 
CPU consumption), but sometimes the aRts process runs amok on the CPU (using 
over 90% CPU) and ends up killing itself due to CPU overload. This does NOT 
happen if you run aRts on the ALSA hardware device. Now it's hard to tell where 
exactly in the stack the bug is. And yes, we've tried setting up aRts to use 
the ESD protocol instead, that was even worse. Any ideas? (And I know aRts is 
legacy stuff, it might become less of an issue over time, still it would be 
nice if we could get the issues with the aRts+PA setup fixed.) If you think 
aRts is broken, we can of course fix it, but we need to know what's broken and 
why this only happens with PA.

        Kevin Kofler




More information about the fedora-devel-list mailing list