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 #794316,
regarding can't unlock desktop: Too many open files (inotify fds leaked on
unsuccessful login)
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.)
--
794316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794316
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.14.1-7
Severity: serious
This occurred on a jessie system using the default GNOME 3 desktop.
My laptop screen had been locked for a while. I typed the password and
nothing happened. After a few seconds, the screen went blank again.
Looking at journalctl I observed:
gdm-session-worker[23803]: <5>AccountsService: Failed to monitor logind
session changes: Too many open files
I looked in Google and I came across some instructions at
https://bugzilla.redhat.com/show_bug.cgi?id=1081004
and I tried them:
# loginctl list-sessions
SESSION UID USER SEAT
150 1000 daniel seat0
352 1000 daniel
2 sessions listed.
# loginctl show-session 150
Id=150
Name=daniel
Timestamp=Fri 2015-07-31 08:16:35 CEST
TimestampMonotonic=58211655247
VTNr=7
Display=:0
Remote=no
Service=gdm-password
Scope=session-150.scope
Leader=9094
Audit=150
Type=x11
Class=user
Active=yes
State=active
IdleHint=yes
IdleSinceHint=1438349828896720
IdleSinceHintMonotonic=68154456351
# loginctl unlock-session 150
The unlock-session command unlocked the screensaver and I was able to
see the desktop again.
--- 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 ---
