Your message dated Sun, 29 Jan 2017 14:58:25 +0000
with message-id <[email protected]>
and subject line Re: Bug#799179: May have been fixed upstream
has caused the Debian Bug report #799179,
regarding gdm3: locking the screen leaks gdm-session-worker processes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
799179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799179
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.14.2-2
Severity: normal
Hi,
everytime I lock the GNOME session and unlock it again a new
gdm-session-worker process is created.
Here's what the process list looks like after some hours of uptime:
$ ps ax|grep gdm-session-worker
718 ? Sl 0:00 gdm-session-worker [pam/gdm-password]
720 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
2583 ? Sl 0:01 gdm-session-worker [pam/gdm-password]
3003 ? Sl 0:00 gdm-session-worker [pam/gdm-password]
3005 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
8132 ? Sl 0:00 gdm-session-worker [pam/gdm-password]
8134 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
8832 ? Sl 0:00 gdm-session-worker [pam/gdm-password]
8834 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
9547 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
9568 ? Sl 0:00 gdm-session-worker [pam/gdm-password]
9570 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
10081 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
10098 ? Sl 0:00 gdm-session-worker [pam/gdm-password]
10100 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
10608 ? Sl 0:00 gdm-session-worker [pam/gdm-password]
10609 ? Sl 0:00 gdm-session-worker [pam/gdm-fingerprint]
[...]
I also tried with gdm3 3.17.90-1 from experimental but that doesn't
solve the problem.
Regards,
Berto
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gdm3 depends on:
ii accountsservice 0.6.40-3
ii adduser 3.113+nmu3
ii dconf-cli 0.24.0-2
ii dconf-gsettings-backend 0.24.0-2
ii debconf [debconf-2.0] 1.5.57
ii flwm [x-window-manager] 1.02+git2015.04.29-1
ii gir1.2-gdm3 3.14.2-2
ii gnome-session [x-session-manager] 3.16.0-1
ii gnome-session-bin 3.16.0-1
ii gnome-settings-daemon 3.16.3-1
ii gnome-shell 3.16.3-2
ii gnome-terminal [x-terminal-emulator] 3.16.2-1
ii gsettings-desktop-schemas 3.16.1-1
ii libaccountsservice0 0.6.40-3
ii libaudit1 1:2.4.4-1
ii libc6 2.19-19
ii libcanberra-gtk3-0 0.30-2.1
ii libcanberra0 0.30-2.1
ii libgdk-pixbuf2.0-0 2.31.5-1
ii libgdm1 3.14.2-2
ii libglib2.0-0 2.44.1-1.1
ii libglib2.0-bin 2.44.1-1.1
ii libgtk-3-0 3.16.6-1
ii libpam-modules 1.1.8-3.1
ii libpam-runtime 1.1.8-3.1
ii libpam-systemd 225-1
ii libpam0g 1.1.8-3.1
ii librsvg2-common 2.40.10-1
ii libselinux1 2.3-2+b1
ii libsystemd0 225-1
ii libwrap0 7.6.q-25
ii libx11-6 2:1.6.3-1
ii libxau6 1:1.0.8-1
ii libxdmcp6 1:1.1.2-1
ii libxrandr2 2:1.5.0-1
ii lsb-base 9.20150826
ii metacity [x-window-manager] 1:3.17.2-4
ii mutter [x-window-manager] 3.16.3-1
ii policykit-1 0.105-11
ii ucf 3.0030
ii x11-common 1:7.7+9
ii x11-xserver-utils 7.7+5
ii xterm [x-terminal-emulator] 320-1
Versions of packages gdm3 recommends:
ii at-spi2-core 2.16.0-1
ii desktop-base 8.0.2
ii gnome-icon-theme 3.12.0-1
ii gnome-icon-theme-symbolic 3.12.0-1
ii x11-xkb-utils 7.7+2
ii xserver-xephyr 2:1.17.2-1.1
ii xserver-xorg 1:7.7+9
ii zenity 3.16.3-1
Versions of packages gdm3 suggests:
ii gnome-orca 3.16.2-2
ii libpam-gnome-keyring 3.16.0-4
-- debconf information:
gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3
--- End Message ---
--- Begin Message ---
Version: 3.22.1-2
On Tue, 22 Mar 2016 at 18:48:54 +0000, Martin wrote:
> May have been fixed upstream:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1241227
>
> Which may also fix:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796718
Yes, I think this has been fixed upstream (although I'm not certain
when, and unfortunately the Red Hat bug doesn't indicate which specific
patches they backported). I can't reproduce #799197 in the Debian
stretch VM where I was testing a fix for #789118, but I could reproduce
it on a similarly-configured jessie VM.
#794316 appears to be a more serious symptom of essentially the same
thing as #799197: I can't reproduce escalating numbers of processes
with inotify handles on stretch.
Conservatively assuming the fixed version is the one I tested,
although in reality I expect it was sometime around 3.16 or 3.18.
Regards,
S
--- End Message ---
