[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

[Daniel Richard G.]

This occurs whether the user logs in (through lightdm) on the console,
or remotely via xrdp.

Running that command, as root, after the user (skunk) has logged in via
lightdm:

    # loginctl list-sessions
    SESSION  UID USER  SEAT  TTY
          2    0 root           
         c2 1000 skunk seat0    

    2 sessions listed.

After logout:

    # loginctl list-sessions
    SESSION  UID USER    SEAT  TTY
          2    0 root             
         c2 1000 skunk   seat0    
         c3  107 lightdm seat0    

    3 sessions listed.

Even after SIGINT to "systemd --user", even after all the user processes
go away, the c2 session remains present.

The output from loginctl for an xrdp login is similar. After logout:

    # loginctl list-sessions
    SESSION  UID USER    SEAT  TTY
          2    0 root             
         c1  107 lightdm seat0    
         c2 1000 skunk

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1871726

Title:
  "systemd --user" and child processes fail to exit when user logs out

Status in systemd package in Ubuntu:
  New

Bug description:
  This concerns systemd 245.2-1ubuntu2 in Ubuntu focal.

  I am using the Xfce desktop. After the user logs out from a desktop
  session, numerous desktop-related processes are left over. Here is a
  listing, taken over twenty minutes after logout:

  skunk        853  0.0  0.2  18912 10300 ?        Ss   17:55   0:00 /lib/systemd/systemd --user
  skunk        854  0.0  0.0 103304  3496 ?        S    17:55   0:00 (sd-pam)
  skunk        881  0.0  0.1   8076  5324 ?        Ss   17:55   0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
  skunk        970  0.0  0.1 305364  6776 ?        Ssl  17:55   0:00 /usr/libexec/at-spi-bus-launcher
  skunk        975  0.0  0.1   7352  4452 ?        S    17:55   0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
  skunk        979  0.0  0.1 230196  5900 ?        Sl   17:55   0:00 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd
  skunk        992  0.0  0.1 239704  7676 ?        Ssl  17:55   0:00 /usr/libexec/gvfsd
  skunk        997  0.0  0.1 378332  6444 ?        Sl   17:55   0:00 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
  skunk       1133  0.0  0.1 156116  5596 ?        Sl   17:56   0:00 /usr/libexec/dconf-service
  skunk       1139  0.0  0.1 236884  4828 ?        Sl   17:56   0:00 /usr/libexec/geoclue-2.0/demos/agent
  skunk       1186  0.0  0.8  59324 34792 ?        S    17:56   0:00 /usr/bin/python3 /usr/share/system-config-printer/applet.py
  skunk       1201  0.0  0.6 391676 25688 ?        Ssl  17:56   0:00 /usr/libexec/evolution-source-registry
  skunk       1224  0.0  0.8 616644 35492 ?        Sl   17:56   0:00 /usr/libexec/goa-daemon
  skunk       1235  0.0  0.7 708928 30512 ?        Ssl  17:56   0:00 /usr/libexec/evolution-calendar-factory
  skunk       1243  0.0  0.2 314744  8980 ?        Sl   17:56   0:00 /usr/libexec/goa-identity-service
  skunk       1271  0.0  0.7 681460 29344 ?        Ssl  17:56   0:00 /usr/libexec/evolution-addressbook-factory
  skunk       1302  0.0  0.1  43968  6432 ?        Ss   17:56   0:00 /usr/lib/bluetooth/obexd
  skunk       1322  0.0  0.2 313872  9076 ?        Ssl  17:56   0:00 /usr/libexec/gvfs-udisks2-volume-monitor
  skunk       1327  0.0  0.1 235684  6468 ?        Ssl  17:56   0:00 /usr/libexec/gvfs-mtp-volume-monitor
  skunk       1331  0.0  0.1 237956  6876 ?        Ssl  17:56   0:00 /usr/libexec/gvfs-gphoto2-volume-monitor
  skunk       1335  0.0  0.1 235864  5760 ?        Ssl  17:56   0:00 /usr/libexec/gvfs-goa-volume-monitor
  skunk       1339  0.0  0.2 316716  8800 ?        Ssl  17:56   0:00 /usr/libexec/gvfs-afc-volume-monitor
  skunk       1347  0.0  0.1 313684  7836 ?        Sl   17:56   0:00 /usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0
  skunk       1353  0.0  0.1 162128  6028 ?        Ssl  17:56   0:00 /usr/libexec/gvfsd-metadata

  
  When a user logs out of the system, all processes associated with the login session should be terminated (barring the use of nohup(1) or the like).

  If I sent a SIGINT to the "systemd --user" process above (PID 853),
  then all the processes promptly go away. This needs to occur on
  logout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions