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

[Mr riaas mokiem]

 > If you issue a `systemctl --user restart pulseaudio`, does it take a long time too?This is how I originally verified that it took too long. I don't remember exactly whether I tried this "restart" specifically or whether I just used "stop" and then "start" but my best guess is that i tried it both ways. I don't think it matters though as it should be pretty much equivalent. And of course, I also verified that it took a long time during boot too.

    On Tuesday, November 6, 2018, 3:00:28 PM GMT+1, Felipe Sateler <fsateler at debian.org> wrote:  
 
 

On Sat, Nov 3, 2018 at 2:19 PM Mr riaas mokiem <riaasm at yahoo.com> wrote:

 Here's the output:$ /usr/lib/rtkit/rtkit-test Max realtime priority is: 20
Min nice level is: -15
Rttime limit is: 200000 ns
before:
        SCHED_RESET_ON_FORK: no
        SCHED_OTHER with nice level: 0
Successfully became high priority.
after high priority:
        SCHED_RESET_ON_FORK: yes
        SCHED_OTHER with nice level: -10
Successfully became realtime.
after realtime:
        SCHED_RESET_ON_FORK: yes
        SCHED_RR with priority 10
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.


You can find the logs with `journalctl --unit rtkit-daemon.service`.
But these show rtkit working OK. Maybe it has problems during boot.
If you issue a `systemctl --user restart pulseaudio`, does it take a long time too? 
-- 

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