Comment 2 for bug 1871543

The issue is on my workstation which might have all kind of config history.
On a fresh focal system it looks like "default off, start works"

root@f:~# systemctl status rtkit-daemon
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
     Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor preset: enabled)
     Active: inactive (dead)

root@f:~# systemctl start rtkit-daemon.service
root@f:~# systemctl status rtkit-daemon
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
     Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled; vendor preset: enabled)
     Active: active (running) since Wed 2020-04-08 06:12:27 UTC; 1s ago
   Main PID: 76699 (rtkit-daemon)
      Tasks: 3 (limit: 38284)
     Memory: 684.0K
     CGroup: /system.slice/rtkit-daemon.service
             └─76699 /usr/libexec/rtkit-daemon

Apr 08 06:12:27 f systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Apr 08 06:12:27 f systemd[1]: Started RealtimeKit Scheduling Policy Service.
Apr 08 06:12:27 f rtkit-daemon[76699]: Successfully called chroot.
Apr 08 06:12:27 f rtkit-daemon[76699]: Successfully dropped privileges.
Apr 08 06:12:27 f rtkit-daemon[76699]: Successfully limited resources.
Apr 08 06:12:27 f rtkit-daemon[76699]: Running.
Apr 08 06:12:27 f rtkit-daemon[76699]: Canary thread running.
Apr 08 06:12:27 f rtkit-daemon[76699]: Watchdog thread running.