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

Felipe Sateler fsateler at debian.org
Tue Jul 8 20:53:37 UTC 2014


On Mon, Jul 7, 2014 at 6:50 AM, Wouter Van Hemel
<wouter-debian at publica.duodecim.org> wrote:
> 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.

This may be the problem, according to google, as this conflicts with
PrivateTmp. Why do you have such a setup? Does it work if you remove
the symlink?

-- 

Saludos,
Felipe Sateler



More information about the pkg-multimedia-maintainers mailing list