Bug#1072930: libpam-wtmpdb: sessions not closed after systemd-run --user --machine …@.host

Luca Boccassi bluca at debian.org
Sat Jul 27 16:41:57 BST 2024


On Sat, 27 Jul 2024 16:50:55 +0200 Chris Hofstaedtler <zeha at debian.org>
wrote:
> Control: reassign -1 src:systemd
> Control: affects -1 libpam-wtmpdb
> 
> Luca,
> 
> On Mon, Jun 10, 2024 at 03:26:24PM +0100, Tomas Janousek wrote:
> > If I do the following:
> > 
> >     $ sudo systemd-run --user -M "$USER"@.host --quiet --wait --
collect --pipe echo foo
> > 
> > then I get an error in the journal:
> > 
> >     Jun 10 14:15:08 deb1-wtmpdb systemd[657]: Started run-
u7.service - echo foo.
> >     Jun 10 14:15:08 deb1-wtmpdb (sd-pam)[1297]:
pam_unix(login:session): session closed for user debian
> >     Jun 10 14:15:08 deb1-wtmpdb (sd-pam)[1297]:
pam_wtmpdb(login:session): update_logout: Updating logout time did not
return SQLITE_DONE: 8
> > 
> > and the session stays open:
> > 
> >     $ last
> >     debian                                 Mon Jun 10 14:15 - still
logged in
> 
> 
> I'll need your help/insight here. ISTM systemd is restricting what
> PAM is allowed to do, but the libpam-wtmpdb cannot really function
> without writing to its file.
> 
> How is this supposed to work?
> Was there a discussion with wtmpdb upstream?

Sorry I am completely clueless about pam, please ask upstream on the
mailing list or on a ticket

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240727/a6e1c5e8/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list