On Sat, Nov 3, 2018 at 2:19 PM Mr riaas mokiem <ria...@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
