Comment 29 for bug 1357252

This still needs further investigation bug I think what's happening is that cgmanager is racing with dbus. And since other jobs refer to cgmanager they end up starting too early, resulting in the possibility that the session init starts too early (before it's been cgroup-constrained).

If correct, he solution to this problem is simple - change cgmanagers 'start on' condition to:

    start on started dbus

Currently, cgmanager *may* start before D-Bus because the 'start on' condition is optimised to start cgmanager as soon as *its* requirements are met. However, this seems nonsensical in this scenario because although cgmanager is starting as early as it can, at the point it starts D-Bus may not be running so clients cannot actually make use of cgmanager yet!

Please could those affected by this problem test on their hardware to see if they can still recreate the problem after running the following:

$ sudo mount -oremount,rw /
$ echo "start on started dbus" | sudo tee -a /etc/init/cgmanager.override
$ sudo reboot