<html><head></head><body><div class="ydp63cb3641yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div>Here's the output:</div><div><div><span>$ /usr/lib/rtkit/rtkit-test </span></div><span>Max realtime priority is: 20<br>Min nice level is: -15<br>Rttime limit is: 200000 ns<br>before:<br> SCHED_RESET_ON_FORK: no<br> SCHED_OTHER with nice level: 0<br>Successfully became high priority.<br>after high priority:<br> SCHED_RESET_ON_FORK: yes<br> SCHED_OTHER with nice level: -10<br>Successfully became realtime.<br>after realtime:<br> SCHED_RESET_ON_FORK: yes<br></span><div><span> SCHED_RR with priority 10</span></div><div><span></span><br></div><div>I'm not sure where to find logs for rtkit during startup though. I also don't know if any recent system updates have changed this rtkit-test output since I reported this bug.<br></div><span><br></span><br></div><div><br></div>
</div><div id="yahoo_quoted_1363550484" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, October 30, 2018, 1:43:52 PM GMT+1, Felipe Sateler <fsateler@debian.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv2993440048"><div><div dir="ltr"><div dir="ltr"><br clear="none"><br clear="none"><div class="yiv2993440048gmail_quote"><div dir="ltr">On Sat, Oct 13, 2018 at 3:09 AM Mr riaas mokiem <<a rel="nofollow" shape="rect" ymailto="mailto:riaasm@yahoo.com" target="_blank" href="mailto:riaasm@yahoo.com">riaasm@yahoo.com</a>> wrote:<br clear="none"></div><blockquote class="yiv2993440048gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div><div class="yiv2993440048gmail-m_809122955068676136ydp79c8fa8eyahoo-style-wrap" style=""><div></div>
<div>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). <br clear="none"></div><div><br clear="none"></div><div>I made one log with the default timeout of systemd, showing that it times out, <span><span>pulseaudio_system_log_timeout.txt</span></span></div><div>I made another one where I set the timeout to 5 minutes, <span><span>pulseaudio_system_log.txt</span></span></div><div><span><span><br clear="none"></span></span></div><div><span><span>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.</span></span></div></div></div></blockquote><div><br clear="none"></div><div>I'm not sure what is going on. However, I see this:</div><div><br clear="none"></div><div><pre class="yiv2993440048gmail-aLF-aPX-K0-aPE" style="">Failed to acquire real-time scheduling: Input/output error</pre><pre class="yiv2993440048gmail-aLF-aPX-K0-aPE" style=""><br clear="none"></pre>This suggests rtkit is for some reason not working properly. Could you run /usr/lib/rtkit/rtkit-test and copy the output?</div><div><br clear="none"></div><div>The logs for rtkit during startup could be useful too.</div><div class="yiv2993440048yqt2829696790" id="yiv2993440048yqtfd59541"><div><br clear="none"></div></div></div><div class="yiv2993440048yqt2829696790" id="yiv2993440048yqtfd52517">-- <br clear="none"><div class="yiv2993440048gmail_signature" dir="ltr"><br clear="none">Saludos,<br clear="none">Felipe Sateler</div></div></div></div></div></div></div>
</div>
</div></body></html>