[svlug] [Robert.L.Harris@rnd-consulting.com: Xupgrade hoses it?]

[Ray Olszewski]

The same thing happened to me yesterday (except is was an upgrade, not a
dist-upgrade, that did it). Check the ownership of /tmp/.X0-lock (assuming
you use Display 0). Make sure it is owned by root, group root, mode 444 .
Other setting may be okay too, but these ones work for me.

(BTW, this was really hard to track down -- took 2 of us about 30 minutes.)

At 09:43 AM 6/25/00 -0600, Robert L. Harris wrote:
>
>I just did a "dist-upgrade" on my debian potato box.  It appears to have 
>upgraded my XF86 3.3.6 and now when I start X, I get this:
>
>bob:/home/nomad>startx
>
>
>X:  server socket directory has suspiciou ownership, aborting.
>_X11TransSocketUNIXConnect: Can't connect: errno = 111
>giving up.
>xinit:  Connection refused (errno 111):  unable to connect to X server
>xinit:  No such process (errno 3):  Server error.



--
------------------------------------"Never tell me the odds!"---
Ray Olszewski                                        -- Han Solo
Palo Alto, CA           	 	         ray at comarre.com        
----------------------------------------------------------------