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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ie8iWFHC0oa7wG+i
	slfmLnlnHSV1imCigqnk4teT9hRiJhhHdd4t4DeKsNhOb6xAmRP8xfIJMnD7G5b3
	TegP6QI/u7zAXoJwNptcV5vmkIf9tS0kGs0Hl8ZzVV/cwdmdeXPbjjfPcKJW0FwV
	1PqoCH+elx2mNl9y6e5xCd2LI9Y=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=cJppxWkJEsawqJnNnPc19X
	ywvdU=; b=XjFq7KN3mlvNQ7YZh40YSPS01yB3zHn3fbNsMnocFp/dYVivA0n6Kx
	pFMFJENm2HXkuPRtZWx881urOt/3jFhpsav1kd2hW0SgH2buijnLEhlsVKuJynoA
	sxVJAba2N/l/xoCLa8Kc+GHInmNXRrQLnY/9MV3F7KU0vtn+JWgwQ=
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=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=greywolf, Greywolf, firewall, Hx-spam-relays-external:ESMTPA
X-HELO:	out2-smtp.messagingengine.com
X-ME-Sender:	<xms:EI7fWXDccOBd9cQ5edCfyzavQGpQr3H0XNZ1Et0n7XNdgjoluOzOYg>
Subject:	Re: Cygwin/X11 - the X11 server won't start.
To:	Greywolf <greywolf AT starwolf DOT com>,
	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<fa352cd4-9317-dbd0-18e6-eafd7f6efdd7 AT starwolf DOT com>
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID:	<8beb3b59-372f-f234-a6ca-570025a5d131@dronecode.org.uk>
Date:	Thu, 12 Oct 2017 16:45:17 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version:	1.0
In-Reply-To:	<fa352cd4-9317-dbd0-18e6-eafd7f6efdd7@starwolf.com>

On 12/10/2017 01:51, Greywolf wrote:
> Just got a new laptoy (Lenovo ThinkPad P51) with an nVidia display 
> adapter as well as Intel integrated graphics.  X11 doesn't start.  
> Everything seems to be fine until it reports back "cannot connect to 
> display :0.0"
> 
> The five-year-old Dell I had worked just fine, no problems, no issue.
> 
> CPU: Xeon E3-1510M
> RAM: 32G
> OS: Windows 10, build 15063.rs2_release.170317-1834
> Various program versions: attached cygcheck-sr.log
> 
> Attached:
> startxwin.log - the output from 'startxwin'
> cygcheck-sr.log - the output from 'cygcheck -sr'
> 
> I see nothing in there to indicate why it cannot open display :0.  [if 
> attachments aren't acceptable, please advise as to what would be an 
> acceptable to submit 192kB of output.]

This log shows that the internal helper clients that the X server starts 
in multiwindow mode aren't able to connect to the X server.

> winInitMultiWindowWM - DISPLAY=:0.0
> winMultiWindowXMsgProc - DISPLAY=:0.0
> winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
> winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
> winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
> winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
> winMultiWindowXMsgProc - Could not open display, try: 3, sleeping: 5
> winInitMultiWindowWM - Could not open display, try: 3, sleeping: 5
> winMultiWindowXMsgProc - Could not open display, try: 4, sleeping: 5
> winInitMultiWindowWM - Could not open display, try: 4, sleeping: 5
> winMultiWindowXMsgProc - Could not open display, try: 5, sleeping: 5
> winInitMultiWindowWM - Could not open display, try: 5, sleeping: 5
> winInitMultiWindowWM - Failed opening the display.  Exiting.
> winMultiWindowXMsgProc - Failed opening the display.  Exiting.

You can probably confirm that's what's preventing the server from 
starting by trying 'X -noclipboard' and seeing if that succeeds.

It looks like something is preventing Cygwin's unix domain socket from 
working.  Since this is emulated using the loopback interface, this 
might be caused by firewall software.

Also, I note that you've installed 32-bit Cygwin.  There really 
shouldn't be any reason not to use 64-bit Cygwin on a new 64-bit system.


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