Bug#886654: systemd : >12 user processes are left running even after checking out of an X Session
Erich Minderlein
erich.minderlein at edhec.com
Mon Jan 8 14:34:10 GMT 2018
Package: systemd
Version: 232-25+deb9u1
Severity: normal
-- Package-specific info:
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-3
ii libaudit1 1:2.6.7-2
ii libblkid1 2.29.2-1
ii libc6 2.24-11+deb9u1
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-4
ii libgcrypt20 1.7.6-2+deb9u2
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-6
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.2+b1
ii libmount1 2.29.2-1
ii libpam0g 1.1.8-3.6
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3+b3
ii libsystemd0 232-25+deb9u1
ii mount 2.29.2-1
ii procps 2:3.3.12-3
ii util-linux 2.29.2-1
Versions of packages systemd recommends:
ii dbus 1.10.24-0+deb9u1
ii libpam-systemd 232-25+deb9u1
Versions of packages systemd suggests:
ii policykit-1 0.105-18
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.130
ii udev 232-25+deb9u1
Hi all
What is :
When checking out from X session as user 1000 and checking in as user 1001,
I had bad performance on my relatively limited notebook.
( different purpose = different user )
I found, as being root, that the following processes were left running,
owned by user 1000(md)
This applies at least to users 1000 and 1001 , on my system, as I use
only these 2 accounts.
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
1 2568 2568 2568 ? -1 Ss 1000 0:00
/lib/systemd/systemd --user
2568 2574 2568 2568 ? -1 S 1000 0:00 (sd-pam)
1 2585 2584 2584 ? -1 Sl 1000 0:00
/usr/bin/gnome-keyring-daemon --daemonize --login
2568 2595 2595 2595 ? -1 Ss 1000 0:00
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile
--systemd-activation
2568 2639 2595 2595 ? -1 Sl 1000 0:00
/usr/lib/dconf/dconf-service
2568 2658 2658 2658 ? -1 Ssl 1000 0:00
/usr/lib/gvfs/gvfsd
2568 2711 2658 2658 ? -1 Sl 1000 0:00
/usr/lib/gvfs/gvfsd-trash --spawner :1.14 /org/gtk/gvfs/exec_spaw/0
2568 2721 2721 2721 ? -1 Ssl 1000 0:00
/usr/lib/gvfs/gvfs-udisks2-volume-monitor
2568 2760 2760 2760 ? -1 Ssl 1000 0:00
/usr/lib/gvfs/gvfs-afc-volume-monitor
2568 2766 2766 2766 ? -1 Ssl 1000 0:00
/usr/lib/gvfs/gvfs-mtp-volume-monitor
2568 2770 2770 2770 ? -1 Ssl 1000 0:00
/usr/lib/gvfs/gvfs-goa-volume-monitor
2568 2774 2774 2774 ? -1 Ssl 1000 0:00
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor
2568 2823 2823 2823 ? -1 Ssl 1000 0:00
/usr/lib/gvfs/gvfsd-metadata
1 3789 3788 3788 ? -1 Sl 1000 0:00
/usr/bin/gnome-keyring-daemon --daemonize --login
X Server / gnome / mate seems not to maintain a log of which processes
are being invoked and with what PID to purpose of killing them properly
What should be:
I feel, that no processes of a checked out user with uid >= 1000 shall
be left unintentionally running after checkout and not survive the
restart of the X server. (
batch, intended background or user cron jobs excluded of course )
Systemd shall do the clean-up after a logout, and make sure that all
processes are terminated or killed properly before the restart of the X
server. with the variety of X servers, graphic Front-ends and console
terminals.
I ask you kindly to modify systemd to clean up properly on log out from
the X or console session , or to forward to the correct package
Best regards Erich Minderlein
More information about the Pkg-systemd-maintainers
mailing list