[systemd-devel] systemd v4[01] and graphical login managers

Christian Hesse list at eworm.de
Fri Feb 10 13:45:09 PST 2012

Cristian Rodríguez <crrodriguez at opensuse.org> on Fri, 10 Feb 2012 18:05:42
> On 09/02/12 14:50, Christian Hesse 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?
> I am having a very similar problem with current HEAD
> "sudo" does no longer work
> % sudo -s
> % id
> uid=1000(crrodriguez)
> su - works, but after typing "exit" it says "killed" (????) downgrading 
> to systemd 37 solves to problem.,

Same problem here. (Did not care a lot as it happens when closing the
This may be related to what I reported in this thread, but it is not
identical. The login manager problem raised with systemd v40 whereas your
problem was present in systemd v39 or before. (Probably you are right and v38
was the first version having this problem.)

BTW, whatever gets killed receives a SIGKILL, I have bash error code 137
(from man bash: The return value of a simple command is [...] 128+n if the
command is terminated by signal n).
Best regards,
                         O< ascii ribbon campaign
                   stop html mail - www.asciiribbon.org

More information about the systemd-devel mailing list