public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Subject: startx xauth unknown command (was Re: Installing X11 on a Dell E6440)
Date: Tue, 08 Mar 2016 11:54:00 -0000	[thread overview]
Message-ID: <56DEBD61.7070702@dronecode.org.uk> (raw)
In-Reply-To: <56D1DCF0.7040005@gmail.com>

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

      parent reply	other threads:[~2016-03-08 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 13:57 Installing X11 on a Dell E6440 Robert Haskins
2016-02-27 17:29 ` Marco Atzeri
2016-02-28  4:25   ` Robert Haskins
2016-02-28  7:44     ` Marco Atzeri
2016-02-29 16:58       ` Robert Haskins
2016-03-08 11:54   ` Jon Turney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56DEBD61.7070702@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).