Package: libpam-cgfs Version: 2.0.1-1 Severity: critical Justification: breaks unrelated software
Hi, The default configuration of libpam-cgfs breaks systemd user session management. All the processes started by systemd --user are not properly put in the correct systemd cgroup. This can be verified with "loginctl user-status" command. This is at least breaking stuffs like policykit. Removing "name=systemd" from the call to the pam module seems to fix this. I don't think it's the role of libpam-cgfs to mangle with systemd cgroups. Regards, Laurent Bigonville -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
