[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#305858: marked as done (xserver-xfree86 leaks client connections)

Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <45D0ECC1.3050909@ens-lyon.org>
and subject line ping timeout, closing
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-12.0.1

I'm getting client connections refused due to what is claimed to be too many
clients:

$ xlsclients
Xlib: connection to ":0.0" refused by server
Xlib: Maximum number of clients reached
xlsclients:  unable to open display ":0.0"

But looking at the /proc/.../fd directory for the X server, I see only a few
dozen connections:

/proc/7032/fd# ls
0  10  12  14  16  18  2   21  26  4  6  8
1  11  13  15  17  19  20  22  3   5  7  9
kegstand:/proc/7032/fd# ls -l
total 24
l-wx------  1 root root 64 Apr 22 10:40 0 -> /var/log/XFree86.0.log
lrwx------  1 root root 64 Apr 22 10:40 1 -> socket:[5151481]
lrwx------  1 root root 64 Apr 22 10:40 10 -> socket:[5151729]
lrwx------  1 root root 64 Apr 22 10:40 11 -> socket:[5151758]
lrwx------  1 root root 64 Apr 22 10:40 12 -> socket:[6487378]
lrwx------  1 root root 64 Apr 22 10:40 13 -> socket:[5151967]
lrwx------  1 root root 64 Apr 22 10:40 14 -> socket:[5152000]
lrwx------  1 root root 64 Apr 22 10:40 15 -> socket:[5152034]
lrwx------  1 root root 64 Apr 22 10:40 16 -> socket:[5164336]
lrwx------  1 root root 64 Apr 22 10:40 17 -> socket:[5152062]
lrwx------  1 root root 64 Apr 22 10:40 18 -> socket:[5152118]
lrwx------  1 root root 64 Apr 22 10:40 19 -> socket:[5152232]
l-wx------  1 root root 64 Apr 22 10:40 2 -> /var/log/gdm/:0.log
lrwx------  1 root root 64 Apr 22 10:40 20 -> socket:[5152291]
lrwx------  1 root root 64 Apr 22 10:40 21 -> socket:[5152360]
lrwx------  1 root root 64 Apr 22 10:40 22 -> socket:[7017086]
lrwx------  1 root root 64 Apr 22 10:40 26 -> socket:[5196140]
lrwx------  1 root root 64 Apr 22 10:40 3 -> /dev/tty7
l-wx------  1 root root 64 Apr 22 10:40 4 -> /proc/mtrr
lrwx------  1 root root 64 Apr 22 10:40 5 -> /dev/dri/card0
lrwx------  1 root root 64 Apr 22 10:40 6 -> /dev/input/mice
lrwx------  1 root root 64 Apr 22 10:40 7 -> socket:[5151557]
lrwx------  1 root root 64 Apr 22 10:40 8 -> socket:[5151562]
lrwx------  1 root root 64 Apr 22 10:40 9 -> socket:[5151672]

-- 
Brian Ristuccia
brian@ristuccia.com

--- End Message ---
--- Begin Message --- 
I am closing this bug since the submitter did not reply to the ping I
send a couple weeks ago. If anybody ever reproduces this problem, feel
free to reopen.

Brice

--- End Message ---
Reply to: