This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: XCloseDisplay + XOpenDisplay fails
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-xfree at cygwin dot com
- Cc: "rurban at x-ray dot at" <rurban at x-ray dot at>
- Date: Sat, 11 Jul 2009 17:36:06 +0100
- Subject: Re: XCloseDisplay + XOpenDisplay fails
- References: <6910a60907100142j461a8edled891a10357c5122@mail.gmail.com>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: cygwin-xfree at cygwin dot com
On 10/07/2009 09:42, Reini Urban wrote:
With the latest server and cygwin-1.7 my previous xlib test form clisp
new-clx fail.
XCloseDisplay() => okay
but all subsequent XOpenDisplay() to the same display fail now with
"No protocol specified".
This worked before. I've also enabled IPV6, which might be related.
The "No protocol specified" message seems to be a bit obtuse. I looked into
it when it was reported here [1] (which of course I can't reproduce now :-( )
It comes back from the server when an attempt is made to open a connection,
and really means something like "No authorization method specified" - the
client didn't offer any authorization data and the peer address wasn't
available or wasn't on the host access list.
I'm afraid I don't know why it happens.
I assume you are starting the server using startx or otherwise providing an
-auth argument? A workaround might be to not to do that.
It might be informative to see if anything relevant is logged with '-audit 2'
xorg-server-1.6.2-1 Release: 1.6.2.0 (20090707)
libX11-devel-1.2.1-1
clisp might be challenging, so I rather want confirmations from the
xserver side before I post details.
[1] http://cygwin.com/ml/cygwin-xfree/2009-07/msg00016.html
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/