Message-Id: <201710121606.v9CG6ojC029815@delorie.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:date:subject:from:to:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=WCZNbrN1Fq7O55Yw
	1mCjYvcKRBogCwGR3ID/9miFOj6PHvNDwejHJQdjYVDVV+tbGSjiFglbRhjkxFfM
	2XI445nHXJK5F1jKjaF+g0Hve10kmzMLVKAVD6q3XvUgci3OToWQgRytJOWDYzm5
	zCr42dkb7mZCwjIdGp1tF8sfx1w=
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
SavedFromEmail: greywolf AT starwolf DOT com
Date: Thu, 12 Oct 2017 09:06:08 -0700
Subject: Re: Cygwin/X11 - the X11 server won't start.
From: Greywolf <greywolf AT starwolf DOT com>
To: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>,
        The Cygwin Mailing List <cygwin AT cygwin DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Found the problem.  It has to run as administrator.  Did that and it ran fine.  Still not sure why this was not an issue before. 
Sorry for the trouble. 
Might upgrade to 64 bit, but that means picking out what i have installed. 


                            --*greywolf;/* on the road */
-------- Original message --------From: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk> Date: 10/12/17  08:45  (GMT-08:00) To: Greywolf <greywolf AT starwolf DOT com>, The Cygwin Mailing List <cygwin AT cygwin DOT com> Subject: Re: Cygwin/X11 - the X11 server won't start. 
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