Comment 3 for bug 298011

output of pulseaudio -D -vv:

jdf@jdf-desktop:~$ sudo killall pulseaudio

jdf@jdf-desktop:~$ pulseaudio -D -vv
I: main.c: PolicyKit refuses acquire-high-priority privilige.
I: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
I: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
I: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
I: main.c: Note that real-time/high-priority scheduling is NOT normally required. If you experience crackling or other sound anomalies, consider one or more of the above solutions.
I: main.c: High-priority scheduling enabled in configuration but now allowed by policy. Disabling forcibly.
W: ltdl-bind-now.c: Failed to find original dlopen loader.
I: main.c: daemon startup successful.

I'm under the assumption that the problems regarding not being root would not apply when pulseaudio is started at boot. Is that correct?

I am still having this problem. Randomly, but around every 5 minutes, my audio will completely stop playing for a few seconds and then come back on. The music, video, flash, or whatever else will continue operating, and when the sound starts again it doesn't start where it left off, it is as if it was just muted for a few seconds. Also, the sound is still randomly stopping altogether (albeit not in VLC, only in Flash and totem) and I still have to do the killall and restart pulseaudio at least once a day. I have been hoping with all the updates I've seen since Intrepid was released that this problem would be fixed, but it hasn't been. This is marked as a likely-dupe, but I'm not sure about that. There have been others with similar problems, but their issues seem to have been fixed when the race condition was rectified. My issue was not.

Does anyone have any ideas on how I can further troubleshoot this or gather more information to help this get fixed? Does anyone know where the logs are stored for the Adobe Flash plugin? Maybe they would contain some information. I'm going to restart and check the system logs to see if I can discern anything from that. I'll post the pertinent info if I find any. Any ideas would be greatly appreciated. It's really annoying to have to close my browser and restart pulseaudio every time I want to visit YouTube.