[systemd-devel] systemd --user broken

Kay Sievers kay at vrfy.org
Sat Jul 27 08:04:43 PDT 2013

On Sat, Jul 27, 2013 at 4:50 PM, Léo Gillot-Lamure
<leo.gillot at navaati.net> wrote:
> All these big changes from systemd 205 seem good and yummy, but how do this
> relates to the systemd --user sessions ?
> I used to launch all my desktop components (WM, panel, applets,
> pulseaudio...) using systemd user units, systemd --user itself being
> launched by my display manager, but now it crashes at launch saying "Failed
> to create root cgroup hierarchy: Permission denied" and "Failed to allocate
> manager object: Permission denied".
> Is this a bug, or should a totally new paradigm be used for user sessions ?
> I find it surprising that apparently no one has yelled at this yet, but I
> couldn't find any interesting thread about this issue. I hope it's not me
> being bad at googling.

systemd --user is now always started as a service by PID1, triggered by logind.

$ tree -d /sys/fs/cgroup/systemd/user.slice/
`-- user-2702.slice
    |-- session-1.scope
    `-- user at 2702.service

You need to chown() the cgroup subtree yourself if you start your own
systemd --user.

It all needs still some work how things should work in the end, we are
not quite there to offer a fully working default setup of systemd


More information about the systemd-devel mailing list