Your message dated Sat, 1 Oct 2022 21:32:41 +0200
with message-id <41600aad-42f4-1467-1ea2-24efd42d5...@debian.org>
and subject line Re: Bug#992990: systemd: Does not clean up user session
has caused the Debian Bug report #992990,
regarding systemd: Does not clean up user session
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.)
--
992990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 247.3-6
Severity: normal
Hello,
It seems that the user sessions are not getting cleaned up when it
crashes unexpectedly, and notably the dbus session bus, which can lead
to various oddities. To reproduce:
- logging in from lightdm ($USER is ff)
- the MATE desktop starts
- the attached snapshot shows the dbus-daemon running: not only the ones
for the ff user, but also for lightdm (!?)
- as root in a mate-terminal, run systemctl restart lightdm
- the MATE session thus gets completely interrupted, lightdm shows up
again
- logging in again as $USER ff
- the MATE desktop starts
- the attached snapshot shows that it's still the same dbus-daemon
running: again not only the ones for the ff user, but also for lightdm
These surviging processes are worrying: when a user is not connected,
should there really be such remainings? I understand that a user may be
running e.g. screen sessions, but more than this?
I could check that systemd 249.3-3 from experimental behaves the same
Samuel
-- Package-specific info:
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500,
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500,
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'),
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1,
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.13.0 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-10
ii libapparmor1 2.13.6-10
ii libaudit1 1:3.0.5-1
ii libblkid1 2.36.1-8
ii libc6 2.31-13
ii libcap2 1:2.44-1
ii libcrypt1 1:4.4.18-4
ii libcryptsetup12 2:2.3.5-1
ii libgcrypt20 1.8.7-6
ii libgnutls30 3.7.1-5
ii libgpg-error0 1.38-2
ii libip4tc2 1.8.7-1
ii libkmod2 28-1
ii liblz4-1 1.9.3-2
ii liblzma5 5.2.5-2
ii libmount1 2.36.1-8
ii libpam0g 1.4.0-9
ii libseccomp2 2.5.1-1
ii libselinux1 3.1-3
ii libsystemd0 247.9-1
ii libzstd1 1.4.8+dfsg-2.1
ii mount 2.36.1-8
ii ntp [time-daemon] 1:4.2.8p15+dfsg-1
ii util-linux 2.36.1-8
Versions of packages systemd recommends:
ii dbus 1.13.18-1
Versions of packages systemd suggests:
ii policykit-1 0.105-31
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.140
ii libnss-systemd 247.9-1
ii libpam-systemd 247.9-1
ii udev 247.9-1
-- Configuration Files:
/etc/systemd/journald.conf changed [not included]
/etc/systemd/logind.conf changed [not included]
-- no debconf information
--
Samuel
#include <culture.h>
--- End Message ---
--- Begin Message ---
Hi Samuel
On Wed, 6 Oct 2021 23:58:19 +0200 Samuel Thibault <sthiba...@debian.org>
wrote:
Hello,
Michael Biebl, le sam. 25 sept. 2021 17:36:05 +0200, a ecrit:
> On Thu, 26 Aug 2021 17:21:39 +0200 Samuel Thibault <sthiba...@debian.org>
> wrote:
> > Control: tags -1 wontfix
> >
> > So AIUI, to get a proper cleanup when the X server happens to go away
> > (lightdm restart, or main session process exit), the processes have to
> > notice that the X server went away?
>
> Not sure what to do about this bug report.
> Do you want to keep it open asking for `KillUserProcesses=yes` to be the new
> default?
I understand that the "screen" case makes it quite unlikely that
KillUserProcesses=yes becomes a default. So perhaps we can just close
it.
Yeah, at this point it's unlikely that we reconsider the default for
KillUserProcesses as a fix for screen/tmux/ etc is not in sight.
So I'm closing the bug report. Should the situation regarding
screen/tmux/ change we can re-evaluate.
Regards,
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
