DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=TLDwfByXSIbSzjCY
	8WvPaBBbsr3RM4NeGwv61R608oRXLTJ41guriovn125xSCDUHLbZ05IXPT1EMwCh
	kW6pa4WrZsr6D19ALQ5hFYNsmBdW+/AZCiBOjeR8jlYj0rF8SXZnxFVhgYybpAeB
	iIuQsCVkp7DZOhP2XP1vUJ/+Muk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: X: Authorization required, but no authorization protocol specified
To: cygwin AT cygwin DOT com, cygwin AT cygwin DOT com
References: <67ea3d1202eccadc3fc21e58af6ca4bf AT mhoenicka DOT de>
From: Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
Cc: markus DOT hoenicka AT mhoenicka DOT de
Message-ID: <55C479DA.7000203@dronecode.org.uk>
Date: Fri, 7 Aug 2015 10:26:50 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <67ea3d1202eccadc3fc21e58af6ca4bf@mhoenicka.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 06/08/2015 17:56, Markus Hoenicka wrote:
> I've upgraded my setup yesterday and ran into a problem running the X
> server. X ran just fine before the upgrade, just like any X client I
> threw at it. I'm aware that some defaults have changed in the couple of
> months since I upgraded, and I hope I've done everything the FAQ
> recommends to accommodate these changes. However, no joy.
>
> Starting the X server now is noticeably slower, regardless of how I
> start it (Windows start menu, startx, or my hitherto preferred method
> startxwin). Biggest problem though is that local X clients cannot
> connect. The server output is like this:
>
> $ startxwin /usr/bin/xterm
> xauth:  file /home/markus.hoenicka/.Xauthority does not exist
> xauth:  file /home/markus.hoenicka/.Xauthority does not exist
> xauth:  file /home/markus.hoenicka/.Xauthority does not exist
> xauth:  file /home/markus.hoenicka/.Xauthority does not exist

startxwin is just a shell script (based on the standard startx), which 
invokes xauth to add an authorization cookie to ~/Xauthority (which is 
also passed to the server using the -auth option)

> The file ~/.Xauthority is created during startup, and it is empty
> after the server shuts down. It does not make any difference if I
> remove the empty file before restarting the X server.

It should have some (binary) content while the server is running, but 
that seems to be failing to happen, for some reason.

> As a workaround I can start XWin manually like this:
> /usr/bin/XWin :0 -multiwindow

This works, of course, because this doesn't use -auth.

> However, I suppose the default behaviour of startx and startxwin was not
> intended to perform like this. Did I miss something obvious?

Indeed.

Is there anything unusual about your home directory?

You might try modifying startxwin to remove the -q from xauth -q to see 
if that reveals a bit more information.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple