Your message dated Thu, 30 Oct 2014 16:14:50 +0100 with message-id <[email protected]> and subject line Re: Bug#767365: gdm3 should not depend on pam_systemd / pam_systemd is a NOP when systemd not PID1 has caused the Debian Bug report #767365, regarding gdm3 should not depend on pam_systemd / pam_systemd is a NOP when systemd not PID1 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 767365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767365 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gdm3 Version: 3.14.1-1 Severity: important Hi, gdm3 should not depend on libpam-systemd. libpam-systemd does nothing in case the system has not been booted with systemd as PID1. From the manpage pam_systemd.so If the system was not booted up with systemd as init system, this module does nothing and immediately returns PAM_SUCCESS. So a non existant libpam-systemd is as good as returning PAM_SUCCESS but does not drag in libpam-systemd and thus systemd. Flo -- Florian Lohoff [email protected]
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Le Thu, 30 Oct 2014 15:14:31 +0100, Florian Lohoff <[email protected]> a écrit : > Hi, > gdm3 should not depend on libpam-systemd. libpam-systemd does nothing > in case the system has not been booted with systemd as PID1. > > From the manpage pam_systemd.so > > If the system was not booted up with systemd as init system, > this module does nothing and immediately returns PAM_SUCCESS. > > So a non existant libpam-systemd is as good as returning PAM_SUCCESS > but does not drag in libpam-systemd and thus systemd. GDM (and the rest of the GNOME desktop) requires logind to run and requires a logind session to be registered. logind itself requires either systemd as PID1 or systemd-shim to be running. The dependency against libpam-systemd expresses this requirement. The only (minor) issue I could see here is that the manpage is not accurate and could be updated to talk about systemd-shim. I'm closing this bug report. Cheers, Laurent Bigonville
--- End Message ---
