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.
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.
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 /user.slice/ user-1000. slice/session- 2.scope systemd: /user.slice/ user-1000. slice/session- 2.scope
5:pids:
1:name=
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!