[pulseaudio-tickets] [Bug 95150] Multiple PulseAudio instances on Ubuntu 15.10

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Apr 29 08:30:43 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=95150

--- Comment #11 from Tanu Kaskinen <tanuk at iki.fi> ---
So something gets stuck between

D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.

and

I: [pulseaudio] core-util.c: Failed to acquire high-priority scheduling:
Input/output error

Either setpriority() or rtkit_make_high_priority() gets stuck. I suspect the
latter. We communicate with rtkit via D-Bus, and I would guess that
rtkit-daemon is not responding to our MakeThreadHighPriority() method calls.
The calls time out eventually, which is why we don't get stuck permanently. The
timeout for D-Bus method calls is 30 seconds if I recall correctly, but in case
of failure, we retry several times, so the delay grows much bigger.

You need to debug rtkit to figure out why it doesn't respond.

Multiple pulseaudio instances can be explained by the fact that multiple
applications try to use pulseaudio, and each of them autospawns a new instance.
The spawned instances would otherwise be short-lived, but they get stuck in the
same place as the first instance. Once the first instance gets past the hang,
the extra instances should die eventually.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20160429/7add1fcf/attachment.html>


More information about the pulseaudio-bugs mailing list