12-15-2000
19,118,
3,359
Join Date: Sep 2000
Last Activity: 15 July 2022, 8:51 AM EDT
Location: Asia Pacific, Cyberspace, in the Dark Dystopia
Posts: 19,118
Thanks Given: 2,351
Thanked 3,359 Times in 1,878 Posts
Similar errors are caused by the fact that many implementations of X client/server do not automatically increment to the next available server port. For example, 6000, 6001, 6002, etc. This can cause errors, but I'm not
sure this is your issue.
One way to find out is to use the <B>netstat -c</B> command to watch the connections and ports to the X server(s) and to see what is going on. Also, you can increase the logging level of the X servers to see if you can find out the cause of the error.
If it is a port problem, you can work around this by specifying higher number ports (higher than 6000). Without further information, logfile info, or netstat output, this is the best I have to offer.