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:references:to:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=QMUWfoFLvpMlr1xH
	WQhpr/uYaoloL3cBD/8i3n4WHET2pE38ji2TI/INYzIZU/H4p58RYjd9pI0BK5hV
	P3fH/S6vvnaleMVJ/sSr1M2in4eLzN3sWNV02fg1w8RZ8c0MEPSYykzDfy4DFv8T
	BFoSoxG22eldc/FPcp6u62JRFlY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: startx xauth unknown command (was Re: Installing X11 on a Dell E6440)
References: <CANmBfsZgWVNRuX7nXYpc-rNDa68XuXUd+WDbBTUYF8REC7M96g@mail.gmail.com> <56D1DCF0.7040005@gmail.com>
To: cygwin@cygwin.com
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <56DEBD61.7070702@dronecode.org.uk>
Date: Tue, 8 Mar 2016 11:54:09 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56D1DCF0.7040005@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 27/02/2016 17:29, Marco Atzeri wrote:
> On 27/02/2016 14:57, Robert Haskins wrote:
>
>> { ~ }  » startxwin
>> xauth: (stdin):2:  unknown command "01c8a525b1e7d7cde2587e307895bfa2"
>> xauth: (stdin):3:  unknown command "01c8a525b1e7d7cde2587e307895bfa2"
>> xauth: (stdin):4:  unknown command "01c8a525b1e7d7cde2587e307895bfa2"
>> xauth: (stdin):5:  unknown command "01c8a525b1e7d7cde2587e307895bfa2"
>
>
> this is strange. But it happens also on my X and it works
> so I presume is not the root cause.

Interesting.  This seems to be a long-standing upstream bug with startx 
(of which startxwin is a slightly modified version), (see [1]), that 
startx does not handle correctly the output of xauth when you have more 
than one network interface.

Further, if you have many network interfaces, performing rDNS on all 
their addresses may add significantly to the time it takes to start up 
the X server.

I think the suggestion of patching startx to use $hostname/unix:0 is a 
good one, especially since -nolisten tcp is now the default, the X 
server won't be listening on IP interfaces (... unless someone chooses 
to startx -- -listen tcp --nolisten unix, in which case it will probably 
fail horribly ...)

https://bugs.freedesktop.org/show_bug.cgi?id=13462


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