From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cadalora.default.sbang.uk0.bigv.io (cadalora.default.sbang.uk0.bigv.io [IPv6:2001:41c9:1:424::90]) by sourceware.org (Postfix) with ESMTP id 42CC8383F87E for ; Sun, 14 Jun 2020 10:44:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 42CC8383F87E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dod.no Authentication-Results: sourceware.org; spf=none smtp.mailfrom=sb@dod.no Received: from ITEM-S63383 (cm-84.211.250.118.getinternet.no [84.211.250.118]) by cadalora.default.sbang.uk0.bigv.io (Postfix) with ESMTPSA id 177F5CD42F; Sun, 14 Jun 2020 11:44:32 +0100 (BST) From: Steinar Bang To: Jon Turney Cc: The Cygwin Mailing List Subject: Re: cygwin x11 doesn't start after windows 10 upgrade References: <82aa19db-4855-8436-2f99-8cdc3c8fb57c@dronecode.org.uk> Date: Sun, 14 Jun 2020 12:44:16 +0200 In-Reply-To: <82aa19db-4855-8436-2f99-8cdc3c8fb57c@dronecode.org.uk> (Jon Turney's message of "Sat, 13 Jun 2020 22:15:31 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jun 2020 10:44:36 -0000 >>>>> Jon Turney : > Sorry to hear you are having problems. [1] lists the ways of starting > the X server we think should work [2]. Ok. xlaunch is still on the list in [1] and it has worked fine for me until these problems started. It seems likely that this is something that happened in the recent Win10 upgrade. But the problem is figuring out what, since there isn't much in the way of error messages. :-) > The simplest way to run the X server is using 'XWin' at a command line. > Does that work? Nope. > I'm guessing probably not. Does it hang? Or exit > after doing nothing? It exits after doing nothing. > Does 'XWin -logverbose 3' produce any more information? Unfortunately not. Here it is: sbang@ITEM-S63383:~$ XWin -logverbose 3 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.20.5.0 OS: CYGWIN_NT-10.0-18363 ITEM-S63383 3.1.5-340.x86_64 2020-06-01 08:59 UTC x86_64 OS: Windows 10 [Windows NT 10.0 build 18363] (Win64) Package: version 1.20.5-3 built 2019-09-06 XWin was started with the following command line: XWin -logverbose 3 OsVendorInit - Creating default screen 0 winInitializeScreens - 1 winInitializeScreen - 0 winValidateArgs - Returning. (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: /cygdrive/d/Profiles/sbang/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winGetDisplay: DISPLAY=:0.0 winDetectSupportedEngines - RemoteSession: no winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 00000005 sbang@ITEM-S63383:~$ Thanks! - Steinar