From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81560 invoked by alias); 21 Feb 2017 14:27:45 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 81542 invoked by uid 89); 21 Feb 2017 14:27:43 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=dpi, Hx-languages-length:1809, H*F:D*org.uk, Hx-spam-relays-external:ESMTPA X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 Feb 2017 14:27:42 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 5642B20B36; Tue, 21 Feb 2017 09:27:41 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 21 Feb 2017 09:27:41 -0500 X-ME-Sender: Received: from [192.168.1.102] (host86-141-130-128.range86-141.btcentralplus.com [86.141.130.128]) by mail.messagingengine.com (Postfix) with ESMTPA id D9D6024216; Tue, 21 Feb 2017 09:27:40 -0500 (EST) Subject: Re: XWin no longer working for me with -nolisten tcp? References: <58A77737.5070104@gmail.com> From: Jon Turney Cc: codespunk+cygwin@gmail.com To: cygwin@cygwin.com Message-ID: <026e3bfa-8d70-cac9-2e9a-d8707633ea12@dronecode.org.uk> Date: Tue, 21 Feb 2017 14:27:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <58A77737.5070104@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-02/txt/msg00261.txt.bz2 On 17/02/2017 22:20, Matt D. wrote: > > I just recently formatted and reinstalled Windows 10 x64. I have not > updated anything related to Cygwin and everything version-wise is just > as it was. > > I was previously starting X with the following: > > $ xinit -- -multiplemonitors -multiwindow -clipboard -noprimary -dpi 96 > -nolisten tcp -displayfd 3 3>/c/home/.display > > But now it fails to open the display: > > http://pastebin.com/raw/bLHTWcrS This log doesn't exactly match that command ('-nolisten inet6' rather '-nolisten tcp') Note that since 1.17.0, -nolisten tcp is the default. > [ 21352.125] winInitMultiWindowWM - DISPLAY=:0.0 > [ 21352.125] winMultiWindowXMsgProc - DISPLAY=:0.0 > [ 21354.140] winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5 > [ 21354.140] winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5 > [ 21361.140] winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5 > [ 21361.140] winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5 > [ 21363.671] winDeinitMultiWindowWM - Noting shutdown in progress This seems to indicate that the helper clients can't connect to the X server on the (emulated) unix domain socket, which is causing the X server to be stopped. I can't reproduce this. Conceivably, this might be caused by firewall issues. > I can get around this issue by using "-listen tcp" instead of "-nolisten > tcp" but I don't understand why. This is especially ironic considering Can you show the log for a working X server as well, please? > that this is the complete opposite workaround to what I had to use three > years ago: > > https://cygwin.com/ml/cygwin-xfree/2014-07/msg00017.html -- Jon Turney Volunteer Cygwin/X X Server maintainer -- 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