On Thu, Jul 4, 2013 at 6:30 PM, Kay Sievers <k...@vrfy.org> wrote: > On Fri, Jul 5, 2013 at 2:35 AM, Cristian RodrÃguez > <crrodrig...@opensuse.org> wrote: >> Since systemd 205, Im getting this scary warning >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Starting >> user-1000.slice. >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Created slice >> user-1000.slice. >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Starting User >> Manager for 1000... >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Starting Session 1 >> of user crrodriguez. >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd-logind[423]: New >> session 1 of user crrodriguez. >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd-logind[423]: Linked >> /tmp/.X11-unix/X0 to /run/user/1000/X11-display. >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Started Session 1 >> of user crrodriguez. >> >> Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[725]: Failed at step >> PAM spawning /usr/lib/systemd/systemd: Operation not permitted > > We are just not there, systemd --user is not started at the moment, > the cgroup sub-tree for the user's session is not accessible for the > systemd --user process running under the user's uid. > > Nothing really to worry about, the message should be ignored for now, > we will get there soon ...
does the old method of manually starting user@.service at least still work? I haven't had any time to track the latest release yet... Auke _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel