Bug#794316: can't unlock desktop

[Ignacio G. Dupont]

Hi,
I'm having the same problem, using gdm3 in Debian stable "Jessie" (gdm3 3.14.1-7)
It seems the bug is related to:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799179

I have noticed that gdm-session-worker instances occurs only on unsuccessful login attempts.
Once the fs.inotify.max_user_instances limit is reached /var/log/messages shows error logs like:
Apr  7 10:05:25 jessie gdm-session-worker[3789]: <5>AccountsService: Failed to monitor logind session changes: Too many open files
Apr  7 10:05:42 jessie gdm-session-worker[3805]: <5>AccountsService: Failed to monitor logind session changes: Too many open filesApr  7 10:06:06 jessie gdm-session-worker[3814]: <5>AccountsService: Failed to monitor logind session changes: Too many open filesApr  7 10:06:31 jessie gdm-session-worker[3832]: <5>AccountsService: Failed to monitor logind session changes: Too many open filesApr  7 10:06:37 jessie gdm-session-worker[3852]: <5>AccountsService: Failed to monitor logind session changes: Too many open files...
I have created the following one-liner to get rid of stalled gdm-session-worker instances:

sudo bash -c "pgrep -f gdm-session-worker | grep -v -f <(pgrep -P $(pgrep gdm3)) | xargs kill -9"

It can be set up to run hourly or daily from crontab to avoid reaching the point in which you can no longer unlock the desktop.

Ignacio.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20160409/dd54be25/attachment.html>