Bug#754076: rtkit: Fails to start at boot (failed at step NAMESPACE)

[Wouter Van Hemel]

Package: rtkit
Version: 0.11-1
Severity: normal


Hello,

While checking why GDM isn't starting on Debian Testing, I found a lot of error messages concerning rtkit:

Jul  7 13:15:59 debian systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Jul  7 13:15:59 debian systemd[4355]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Jul  7 13:15:59 debian systemd[1]: rtkit-daemon.service: main process exited, code=exited, status=226/NAMESPACE
Jul  7 13:15:59 debian systemd[1]: Failed to start RealtimeKit Scheduling Policy Service.
Jul  7 13:15:59 debian systemd[1]: Unit rtkit-daemon.service entered failed state.

.... for some reason rtkit-daemon fails to start at boot on this up-to-date Debian Testing system.

Thanks for your time!

  Wouter


PS: I don't know if it's related, but /tmp is a symlink to /var/tmp on this system.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rtkit depends on:
ii  adduser      3.113+nmu3
ii  libc6        2.19-4
ii  libcap2      1:2.22-1.2
ii  libdbus-1-3  1.8.6-1

Versions of packages rtkit recommends:
ii  dbus         1.8.6-1
ii  policykit-1  0.105-6

rtkit suggests no packages.

-- no debconf information