[systemd-devel] systemd v4 and graphical login managers
list at eworm.de
Thu Feb 9 11:57:25 PST 2012
Lennart Poettering <lennart at poettering.net> on Thu, 9 Feb 2012 19:38:39 +0100:
> On Thu, 09.02.12 18:50, Christian Hesse (list at eworm.de) wrote:
> > Hello everybody,
> > starting with systemd v40 I have problems with graphical login managers
> > (tested with lightdm and slim on Arch).
> > After successful user authentication the login manager is killed by
> > systemd-logind with SIGTERM. I think this is because of the changes in
> > commit "logind: if we have to stop a session, kill at least its leader" -
> > not sure though. Anybody else with this problem?
> Yes, there have been similar reports.
Glad to hear I am not the only one... Could not find any reports so far.
> I am not entirely sure what's
> going on here, but it's most likely by code that closes all open fds
> after the PAM session start hook finished in the parent process of login
> processes. It's OK to close all open fds in the child, but it's not OK
> to do so in the parent.
> systemd-logind tracks open sessions by keeping open a FIFO fd to the PAM
> session client. When the session client dies then systemd will see that
> as EOF. Now, if the PAM client side eagerly closes all fds it finds this
> will trigger an immediate end of session.
Can I help tracking this down? Let me know what to do.
I suppose testing with kdm and/or gdm does not help, does it? I am pretty
sure my pam setup is ok.
O< ascii ribbon campaign
stop html mail - www.asciiribbon.org
More information about the systemd-devel