Bug#922647: Info received (Bug#922647: systemd --user no longer running)

Michael Biebl biebl at debian.org
Sat Mar 9 14:00:36 GMT 2019


Am 09.03.19 um 14:10 schrieb Julien Leproust:
> Hi,
> 
> I found the issue.
> 
> When looking for /etc files not belonging to any package, I discovered
> that /etc/pam.d/common-* files are managed by pam-auth-update.
> 
> Most pam profiles were enabled, except "Register user sessions in the
> systemd control group hierarchy", and just enabling it fixed the
> problem. The systemd user service and logind session are now correctly
> started and everything works fine (device permissions, pulseaudio, etc).
> 
> The real issue becomes why this pam profile got disabled in the first
> place.

libpam-systemd uses pam-auth-update as documented.
There is no code in the libpam-systemd package which disables/removes
pam_systemd.so.

So either you have at some point modified /etc/pam.d/common-* yourself
or there is a bug in pam-auth-update.

If I had to guess, the former is more likely.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190309/fa308e6f/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list