X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:cc:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=KPQtzhVi5cNiROemSXqW
	rA/7Q0x2D6iXSvCX3CGbJn1y3Y9oqNQNipx1ax7DUuqsDkU2gv7Um6ThX2Za5THc
	6pZkalbAV2rMfHKELPEoRr9SjpZJcv2wMzA53Bl7Q/B9gls7KKJ+BEBMXuWDhLlH
	mgda1D1SS6EexHjGFLofjpc=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:cc:subject:in-reply-to
	:references:message-id; s=default; bh=eB0adHkHkuDUcrRFzOhPqPAheu
	I=; b=p3zjK/crol7NaNYe5NiagITC0Wh4VCf7EbP5AxXfyBLny0aKnHkGjGHERV
	HGi71Haw9VIBeocHjpirbCibfh4iu5qPt1Gvm2oKadEqflXP4pLMb1hD0E/6PDZm
	zykkOEL4PIyxKn4xNWZqeHBLF6p+HMBUSo/9axwE/UmOX+3ZQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.6 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=no version=3.3.2
X-HELO:	smtprelay06.ispgateway.de
MIME-Version:	1.0
Date:	Thu, 13 Aug 2015 09:05:04 +0200
From:	Markus Hoenicka <markus DOT hoenicka AT mhoenicka DOT de>
To:	Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
Cc:	cygwin AT cygwin DOT com
Subject:	Re: X: Authorization required, but no authorization protocol specified
In-Reply-To:	<55CB6480.6080905@dronecode.org.uk>
References:	<67ea3d1202eccadc3fc21e58af6ca4bf AT mhoenicka DOT de> <55C479DA DOT 7000203 AT dronecode DOT org DOT uk> <114144297d60607a3c87f5fd63fb555a AT mhoenicka DOT de> <55CB6480 DOT 6080905 AT dronecode DOT org DOT uk>
Message-ID:	<01de93834f17fb76318efee2634f5c3f@mhoenicka.de>
X-Sender:	markus DOT hoenicka AT mhoenicka DOT de
User-Agent:	Roundcube Webmail
X-Df-Sender:	bWFya3VzLmhvZW5pY2thQG1ob2VuaWNrYS5kZQ==
X-IsSubscribed:	yes

At 2015-08-12 17:21, Jon TURNEY was heard to say:
> On 12/08/2015 07:22, Markus Hoenicka wrote:
>> At 2015-08-07 11:26, Jon TURNEY was heard to say:
>>> You might try modifying startxwin to remove the -q from xauth -q to
>>> see if that reveals a bit more information.
>> 
>> I finally got round to run this suggested test too. The first time I 
>> try
>> to start X I get the following output:
>> 
>> $ XAUTHORITY="" startxwin /usr/bin/emacs
>> Using authority file /home/<username>/.serverauth.1076
>> Writing authority file /home/<username>/.serverauth.1076
>> Using authority file /home/<username>/.Xauthority
>> Writing authority file /home/<username>/.Xauthority
>> xauth:  file /home/<username>/.Xauthority does not exist
>> xauth:  file /home/<username>/.Xauthority does not exist
>> Using authority file /home/<username>/.Xauthority
>> Writing authority file /home/<username>/.Xauthority
> 
>> Could this be a timing issue while writing to a network drive? 
>> Remember
>> that we use roaming profiles here.
> 
> Yes, I think that the fact it's a network drive is the significant 
> difference.
> 
> But the failure seems utterly crazy. xauth is used to write a file,
> and then moments later another instance of xauth claims it doesn't
> exist.
> 
> I've no idea if this is a problem with xauth, cygwin or your networked
> file system.  Do you know what kind of device the network share is on?
> 

I'm sorry but as a non-IT person I'm not familiar with the devices our 
IT folks run.

> There was another report of some problems with xauth and network file
> system (see the thread starting at [1]), but the symptoms seem very
> different.  Nevertheless you might like to try with xauth -i to see if
> the behaviour is any different.
> 

I've added the -i switch to all xauth calls in startxwin, but that does 
not make a difference except that the first attempt to start an X app 
succeeds. As reported earlier, without the -i switch the *first* attempt 
to start an X client fails, but a second try using the same command 
usually succeeds. However, in either case I cannot run any other X 
clients in addition to the first one.

> Possible workarounds:
> 
> You could edit /usr/bin/startxwin to change 'enable_xauth' to 0, or
> set the XAUTHORITY env var to a local path
> 

Yes, I've done the latter for the past couple of days, and this is 
indeed all it takes to make X work again. As not many seem to be 
affected by a similar setup, I think we should stop here looking for a 
fix until further evidence suggests a solution.

thanks a lot
Markus


-- 
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38


--
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

- Raw text -