[pulseaudio-tickets] [Bug 99356] pulseaudio hangs when rtkit cannot start

[bugzilla-daemon at freedesktop.org]

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

--- Comment #3 from Felipe Sateler <fsateler at gmail.com> ---
I think I have traced the problem.

Rtkit fails to start because PrivateTmp= conflicts with symlinks in /var. This
is a bug in systemd (but I have not filed it yet).

DBus apparently never stops trying to start it, until the timeout is reached
(by default 25 seconds). Thus, one would expect to have pulseaudio have a
delayed start of 25 seconds. Not so, because pa_raise_priority:

    if (set_nice(nice_level) >= 0) {
        pa_log_info("Successfully gained nice level %i.", nice_level);
        return 0;
    }

    for (n = nice_level+1; n < 0; n++)
        if (set_nice(n) >= 0) {
            pa_log_info("Successfully acquired nice level %i, which is lower
than the requested %i.", n, nice_level);
            return 0;
        }

If set_nice fails, pulseaudio will try successively higher nice levels until it
reaches 0 (probably assuming it was started with 0 niceness). nice_level is by
default -11, so there would be 11 calls to set_nice => 11*25 = 4:35 minutes.

BogDan Vatra, if you wait more than 5 minutes, does pulseaudio eventually
start? If this hypothesis is confirmed, then the solution would be to either:

1. Lower the timeout
2. detect that rtkit did not work the first time because dbus could not start
rtkit, and do not try to contact it again in successive retries.

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