Gtk-WARNING **: cannot open display: :0, Maximum number of clients reached
Maximum number of clients reached
(gwenview:18513): Gtk-WARNING **: cannot open display: :0

slackware 64 14.1 kde

I can not open other programs when i run three of it.
if i run dolphin, pidgin and seamonkey i can not open more.
Or if a use skype i can not open other windows and programs

i use this but i dont know whats next
netstat -an --unix | grep X11-unix
and also
lsof -p `pidof X` | grep socket | wc -l


nothing happen.
at this time i only use xfce instead of kde4

my temporary solution its reboot the system many times until the kdeinit want to work.
other thing is not always run programs, ,any times dont run anything, just desktop.

Disable everything, custom Desktop gadgets, moving Desktop backgrounds, eye candy extra features etc until you have something that works. Then enable plugins etc until you find the culprit

There's a pretty long discussion about this error on an old blog post of mine: http://alien.slackbook.org/blog/kde-...are-13-37-rc1/

In particular, it mentions a script that you can run the moment you get this “maximum clients” issue again.
It should list the X client programs that have an active unix socket. It may show you what program is eating up all sockets.

The script is here, http://slackware.com/~alien/tools/xsocket_list.py .
Run it as Eric

Wow, these fedora people must really hate shell scripting with a passion. As far as I can tell that script is more or less the two commands he mentions above spread over 30 lines of Python.

The for loops compare what was returned from the two commands and only prints if there is an inode match. It also skips over any errors. If you just want the output from the two bash commands, then yes you should just run them in bash.

You have no idea how bad it is... I've seen and heard things that would amaze you about Fedora.

Staying out of topic: The lorax tool that creates Anaconda-based installation images is known to be very efficient and has been re-written entirely in python, partly to sort the previous mess. It now looks clean. You can check that yourself:It's not surprising that it be well written, as the Anaconda team includes Slackware Alumni

1 members found this post helpful.

Here's a good question I've been pondering since the topic was posted but... how many UNIX sockets should a system have any way for services? is there a limited number of socket compared to other process methods like pipelining?

i re install after a few months slackware, i dont remember, and apologize with make this post alone. i re install some deps an all fix. thanks to all