Bug#910512: pulseaudio: Pulseaudio takes longer to start than default systemd timeout

[Felipe Sateler]

On Sat, Oct 13, 2018 at 3:09 AM Mr riaas mokiem <riaasm at yahoo.com> wrote:

> I think I've got the log. I had to edit the main pulseaudio.service file
> because it was saying something about "bad unit" when I used the suggested
> command. And I could only find the logs in the main journalctl output (not
> with --user or --unit or --user-unit) so I just grepped on pulseaudio which
> is why the logs also contain some other lines (like dbus for pulseaudio).
>
> I made one log with the default timeout of systemd, showing that it times
> out, pulseaudio_system_log_timeout.txt
> I made another one where I set the timeout to 5 minutes,
> pulseaudio_system_log.txt
>
> I hope this helps. It seems that the startup time went from below 90
> seconds (default systemd timeout) to a bit more than 2 minutes. So I'm not
> sure if there was something else slowing down this startup even before I
> noticed this timeout.
>

I'm not sure what is going on. However, I see this:

Failed to acquire real-time scheduling: Input/output error


This suggests rtkit is for some reason not working properly. Could you
run /usr/lib/rtkit/rtkit-test and copy the output?

The logs for rtkit during startup could be useful too.

-- 

Saludos,
Felipe Sateler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pulseaudio-devel/attachments/20181030/cf01dd8d/attachment.html>