The fix does not work for me:

uname -r
5.4.0-33-generic

ournalctl -b0 -u rtkit-daemon
-- Logs begin at Wed 2020-04-29 18:57:09 EEST, end at Thu 2020-06-04 18:41:05 
EEST. --
Jun 04 18:26:06 n552vw systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
Jun 04 18:26:06 n552vw systemd[1]: Started RealtimeKit Scheduling Policy 
Service.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully called chroot.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully dropped privileges.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully limited resources.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Running.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Canary thread running.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Watchdog thread running.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to