Agreed - proposed fix in 5.4.0-32-generic also works for me. twiggy2@twiggy2:~$ journalctl -b -u rtkit-daemon -- Logs begin at Wed 2020-05-06 22:30:38 BST, end at Tue 2020-05-19 19:32:24 BST. -- May 19 19:32:11 twiggy2 systemd[1]: Starting RealtimeKit Scheduling Policy Service... May 19 19:32:11 twiggy2 systemd[1]: Started RealtimeKit Scheduling Policy Service. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully called chroot. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully dropped privileges. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully limited resources. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Running. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully made thread 1037 of process 1037 owned by '1000' high priority at nice level -11. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Supervising 1 threads of 1 processes of 1 users.
Rest of boot logs appear fine. Thank you ! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
