Your message dated Wed, 23 Aug 2023 00:21:44 +0200
with message-id <8f6b9ef2-1bd6-4622-960b-458cd12f5...@debian.org>
and subject line Re: systemd --user and sd-pam processes keep running after
logout (again)
has caused the Debian Bug report #1023545,
regarding systemd --user and sd-pam processes keep running after logout (again)
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 ow...@bugs.debian.org
immediately.)
--
1023545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 252-2
Severity: normal
Dear Maintainer,
similar to #749268 there seems to be again the problem, that when logging
out, the systemd user process and sd-pam are not killed.
Take, e.g., this example:
# loginctl kill-session 34
# pgrep -a -u pat
11499 /lib/systemd/systemd --user
11500 (sd-pam)
# loginctl list-sessions
SESSION UID USER SEAT TTY
13 0 root seat0 tty2
21 0 root seat0 tty2
25 0 root seat0 tty2
33 0 root seat0 tty2
36 0 root seat0 tty2
37 121 sddm seat0
6 sessions listed.
So although there is no logind session left, there are still the two user
processes around.
I added
KillUserProcesses=yes
but that did not help (is this an additional bug?).
Do I miss anything in order to kill the systemd user process automatically?
Kind regards
Patrick
-- Package-specific info:
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (900, 'stable-security'), (900, 'testing'), (800, 'stable'),
(500, 'unstable-debug'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii libacl1 2.3.1-1
ii libaudit1 1:3.0.7-1.1+b1
ii libblkid1 2.38.1-1.1+b1
ii libc6 2.35-4
ii libcap2 1:2.44-1
ii libcryptsetup12 2:2.5.0-6
ii libfdisk1 2.38.1-1.1+b1
ii libgcrypt20 1.10.1-2
ii libkmod2 30+20220905-1
ii liblz4-1 1.9.4-1
ii liblzma5 5.2.7-0.1
ii libmount1 2.38.1-1.1+b1
ii libseccomp2 2.5.4-1+b1
ii libselinux1 3.4-1+b2
ii libssl3 3.0.7-1
ii libsystemd-shared 252-2
ii libsystemd0 252-2
ii libzstd1 1.5.2+dfsg-1
ii mount 2.38.1-1.1+b1
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.14.4-1
ii systemd-timesyncd [time-daemon] 252-2
Versions of packages systemd suggests:
ii libfido2-1 1.12.0-1
ii libtss2-esys-3.0.2-0 3.2.0-1+b1
ii libtss2-mu0 3.2.0-1+b1
pn libtss2-rc0 <none>
ii policykit-1 122-1
pn systemd-boot <none>
ii systemd-container 252-2
pn systemd-homed <none>
ii systemd-resolved 252-2
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.14.4-1
pn dracut <none>
ii initramfs-tools 0.142
ii libnss-systemd 252-2
ii libpam-systemd 252-2
ii udev 252-2
-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
SystemMaxUse=300M
/etc/systemd/logind.conf changed:
[Login]
KillUserProcesses=yes
/etc/systemd/system.conf changed:
[Manager]
DefaultTimeoutStartSec=20s
DefaultTimeoutStopSec=15s
DefaultDeviceTimeoutSec=20s
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 5 Dec 2022 22:42:11 +0100 Michael Biebl <bi...@debian.org> wrote:
On Sun, 06 Nov 2022 14:37:39 +0100 =?utf-8?q?Patrick_H=C3=A4cker?=
<pa...@web.de> wrote:
> Package: systemd
> Version: 252-2
> Severity: normal
>
> Dear Maintainer,
>
> similar to #749268 there seems to be again the problem, that when logging
> out, the systemd user process and sd-pam are not killed.
>
> Take, e.g., this example:
> # loginctl kill-session 34
>
> # pgrep -a -u pat
> 11499 /lib/systemd/systemd --user
> 11500 (sd-pam)
>
> # loginctl list-sessions
> SESSION UID USER SEAT TTY
> 13 0 root seat0 tty2
> 21 0 root seat0 tty2
> 25 0 root seat0 tty2
> 33 0 root seat0 tty2
> 36 0 root seat0 tty2
> 37 121 sddm seat0
>
> 6 sessions listed.
>
> So although there is no logind session left, there are still the two user
> processes around.
>
> I added
> KillUserProcesses=yes
> but that did not help (is this an additional bug?).
>
> Do I miss anything in order to kill the systemd user process automatically?
>
It looks like
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023545
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024080
might be duplicates.
Assuming this issue is a duplicate of #1024080, which has been reported
to be fixed, I'm closing this bug report.
If you still run into this issue, please let us know so we can reopen
the bug report.
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
