GNOME Bugzilla – Bug 731654
gdm-session-worker [pam/gdm-launch-environment] persists after stopping gdm
Last modified: 2018-05-24 11:03:16 UTC
Hello, On my Debian machine, running systemd, when I'm stopping gdm there is a gdm-session-worker [pam/gdm-launch-environment] that seems to stay forever. When restarting gdm, I'm ending up with two of these processes gdm: 3.12.2
I can confirm this issue. The process gdm-session-worker [pam/gdm-launch-environment] also prevents some other remaining processes related to gdm to shutdown. Once it gets killed manually, all the remaining process go away too. At least for me, the issue is not exactly reproducible. If i start a fresh new gdm and stop it immediately afterwards, without logging in inbetween, then shutdown of gdm works correctly. However, once i start a gnome session via gdm and logout of that session, then trying to stop gdm via a tty shows the behavior described above. I can provide a log (via journalctl) or a list of the other processes if needed.
This also happens when GNOME Shell crashes For each crash, a gdm-session-worker process with ppid 1 remains - it is active and logging to syslog For each crash, an additional process is left behind Normally, two wroker processes exist with the parent being gdm: s -fC gdm-session-worker | cat UID PID PPID C STIME TTY TIME CMD root 1286 1275 0 07:51 ? 00:00:00 gdm-session-worker [pam/gdm-launch-environment] root 1903 1275 0 07:51 ? 00:00:00 gdm-session-worker [pam/gdm-password] ps -fp 1275 | cat UID PID PPID C STIME TTY TIME CMD root 1275 1 0 07:51 ? 00:00:00 /usr/sbin/gdm3 when gdm3 goes away, one of the workers remain with ppid 1
Created attachment 326503 [details] pstree for left-behind process
so we have this in the code: prctl (PR_SET_PDEATHSIG, SIGTERM);• I guess, then, it must be ignoring SIGTERM. Does adding the patch from bug 755291 help?
So, this has been around for close to a year now, right? I just reinstalled gnome-shell because it keeps crashing In this new and improved desperate attempt to have GNOME running at all, gdm fails to restart. Apparently the remaining processes, that has been known about for almost a year, prevents gdm from starting. sudo systemctl restart gdm - is ineffective get-around fortunately, while gnome shell is crashed, virtual consoles work in a virtual console (control+option+fn+F1) sudo killall --user gdm sudo killall gdm-session-worker sudo systemctl restart gdm
One can use lightdm in the meantime This has been broken since 3.18 in 2015
The bug 755291 patch went into 3.19.4 gdm still cannot be restarted sudo systemctl restart gdm.service echo Observed on $(date --utc --rfc-3339=date) && echo $(lsb_release --description --codename --short) && uname --nodename --kernel-release --kernel-version && for _P in gnome-session libwayland-server0 lightdm; do dpkg --status $_P | egrep "^(V|Pa)"; done Observed on 2017-01-12 Ubuntu 16.10 yakkety c93 4.8.0-32-generic #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016 Package: gnome-session Version: 3.20.2-1ubuntu7 Package: libwayland-server0 Version: 1.11.0-2 Package: lightdm Version: 1.19.5-0ubuntu1 It’s a known problem since 2 years in bug 747339
the gdm3 version is Package: gdm3 Version: 3.20.1-1ubuntu2
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/201.