Marin, you are right! No libpam-systemd installed, so no pam_systemd.so file and no "session optional pam_systemd.so" entry in /etc/pam.d /common-session. I've just installed libpam-systemd and logged in and the issue vanished. However, it seems "sudo pam-auth-update" is no handling it automatically, so executing it has no effect (I see just two options: Unix authentication [x] and Create home directory on login [ ]; so no "Create home directory on login" option). There are no customizations in any file.
Now ssh sessions are in the right controller: $ egrep 'systemd|pids' /proc/self/cgroup 5:pids:/user.slice/user-1000.slice/session-2.scope 1:name=systemd:/user.slice/user-1000.slice/session-2.scope and also, for instance, "make -j500" works fine. The system was installed initially from a daily build (about a month ago) and updated/upgraded/dist-upgraded/do-release-upgraded continuously ever since. I'm installing a fresh one to verify if this issue still exists or not. I'll let you know. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561658 Title: ssh sessions don't run in session cgroup but in sshd's -- pam_systemd missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561658/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
