Comment 14 for bug 2015126

Revision history for this message
Steve Langasek (vorlon) wrote :

Ah, now, rechecking, it appears the gdm session is mostly dead:

$ systemctl status session-35.scope --no-pager -l | sed -e's/User .*/User foo/'
× session-35.scope - Session 35 of User foo
     Loaded: loaded (/run/systemd/transient/session-35.scope; transient)
  Transient: yes
     Active: failed (Result: timeout) since Fri 2023-04-21 10:47:20 PDT; 18min ago
        CPU: 2.916s

Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) systemd-logind: releasing fd for 13:65
Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) UnloadModule: "libinput"
Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) systemd-logind: releasing fd for 13:74
Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) UnloadModule: "libinput"
Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) systemd-logind: releasing fd for 13:66
Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) Server terminated successfully (0). Closing log file.
Apr 21 10:47:20 virgil systemd[1]: session-35.scope: Failed with result 'timeout'.
Apr 21 10:47:20 virgil systemd[1]: session-35.scope: Consumed 2.916s CPU time.
$

But there are still some processes owned by the user lingering:

$ ps awxfu|grep ^x | cut -f2- -d' '
     9185 0.0 0.0 18152 10956 ? Ss 09:40 0:04 /lib/systemd/systemd --user
     9186 0.0 0.0 170764 4508 ? S 09:40 0:00 \_ (sd-pam)
     9192 0.0 0.0 48216 6756 ? S<sl 09:40 0:00 \_ /usr/bin/pipewire
     9193 0.0 0.0 32256 6428 ? Ssl 09:40 0:00 \_ /usr/bin/pipewire-media-session
    17778 0.0 0.0 8436 4124 ? Ss 10:47 0:00 \_ /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
    17779 0.0 0.0 471820 7440 ? Ssl 10:47 0:00 \_ /usr/libexec/xdg-document-portal
    17782 0.0 0.0 244796 5416 ? Ssl 10:47 0:00 \_ /usr/libexec/xdg-permission-store
$

Seems like a bug in the session management of those processes? But the actual gdm process is dead, as is gnome-shell.

Could it be an issue of the timer not triggering if the system is suspended when the timeout is reached, and then resumed after?