Comment 2 for bug 1871726

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