Comment 8 for bug 1556447

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks, Stephen, culprit found. The systemd cgroup was yours - until you did a sudo.

For now you can work around this by commenting out the libpam-cgfs line from /etc/pam.d/common-session-noninteractive. Then re-chown your current systemd cgroup to yourself or log back in.

I'm not yet sure whether the proper fix will be to

1. remove the line from noninteractive,
2. have libpam-cgfs check for user-$loginuid.slice in the current systemd cgroup, and create a new one if it doesn't match
3. just add another libpam-cgfs argument to say whether to create a new systemd cgroup, and have it not do so for noninteractive.