On Thu, 22.03.12 13:07, Frederic Crozat (fcro...@suse.com) wrote: > > > Normally, when the pam session close hooks are called logind responds to > > > this by killing the main process of the session if it still > > > exists. This is probably the source of the problem here. > > > > I have now commited a patch to git that might fix your issue. Please > > test: > > > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=75c8e3cffd7da8eede614cf61384957af2c82a29 > > > > I assume this fixes your problem, but since our kernels actually have > > audit enabled I am a bit too lazy trying to reproduce the issue here, so > > I'd be very thankful if you could test this! > > I was hoping it would also fix > https://bugs.freedesktop.org/show_bug.cgi?id=45670 / > https://bugzilla.novell.com/show_bug.cgi?id=746704 but it doesn't :(
This only happens in kdm and the SUSE implementation of sudo, right? My guess is still that for some reason those PAm clients invoke the PAM session end handler way too early. Would be good to trace that down. Just place some debug messages in pam_systemd and check when they are printed. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
