James D. Freels [EMAIL PROTECTED] writes:
The fix as recommended by several folks is to
rm -rf /tmp/.X11-unix
I trust this information is being passed on to the developers without
a formal bug report.
It would be far better to submit a bug report, actually.
-- John
In the recent potato update of the X packages from
3.3.6-7 to 3.3.6-8, it caused it to quit working. I will
file a bug report if not fixed right away. The error
messages on startup are:
X: server socket directory has suspicious ownership, aborting.
_X11TransSocketUNIXConnect: Can't connect:
On Mon, Jun 26, 2000 at 09:35:08AM -0400, James D. Freels wrote:
In the recent potato update of the X packages from
3.3.6-7 to 3.3.6-8, it caused it to quit working. I will
file a bug report if not fixed right away. The error
messages on startup are:
X: server socket directory has
A bunch of us got this. The answer that worked for me was to
cd /tmp
rm -rf .X*
startx
Worked great. There has been discussion on the list as to what
is broken so hopefully the maintainers know about it now.
Robert
Thus spake James D. Freels ([EMAIL PROTECTED]):
In the recent potato
[EMAIL PROTECTED] wrote:
In the recent potato update of the X packages from
3.3.6-7 to 3.3.6-8, it caused it to quit working. I will
file a bug report if not fixed right away.
You might try e.g. bug #66225.
(Executive summary: removing /tmp/.X11-unix allowed it to run again.)
--
Colin Watson
The fix as recommended by several folks is to
rm -rf /tmp/.X11-unix
I trust this information is being passed on to the developers without
a formal bug report.
Thanks to all for responding!!
--
/--\
|James D. Freels, P.E._i,
6 matches
Mail list logo
