From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33569 invoked by alias); 16 Oct 2015 07:10:40 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Received: (qmail 33548 invoked by uid 89); 16 Oct 2015 07:10:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: smtprelay01.ispgateway.de Received: from Unknown (HELO smtprelay01.ispgateway.de) (80.67.29.23) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 16 Oct 2015 07:08:22 +0000 Received: from [80.67.16.136] (helo=webmail.df.eu) by smtprelay01.ispgateway.de with esmtpa (Exim 4.84) (envelope-from ) id 1Zmz7d-0002e3-9F; Fri, 16 Oct 2015 09:08:13 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 16 Oct 2015 07:10:00 -0000 From: Markus Hoenicka To: cygwin-xfree@cygwin.com Cc: paul Subject: Re: Xserver corresponds to display :1.0 instead of :0.0 In-Reply-To: References: Message-ID: <9435151592e14c53459746fe0f3b9480@mhoenicka.de> X-Sender: markus.hoenicka@mhoenicka.de User-Agent: Roundcube Webmail X-Df-Sender: bWFya3VzLmhvZW5pY2thQG1ob2VuaWNrYS5kZQ== X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg00005.txt.bz2 At 2015-10-16 07:41, paul was heard to say: > I have a very simple ~/.startxwinrc: > > xrdb -load $HOME/.Xresources > xterm -display :0.0 # xterm & > exec sleep infinity > > Recently, I found that the xterm wasn't launching. I googled, read > some cygwin threads about X authorities, but have to admit, I have a > lot to learn about X windows. Anyway, since I could open an xterm by > right clicking on the Cygwin/Xserver:1.0 app in the notification area > of Windows 7, I sneakily (OK, it wasn't the craftiest thing in the > world) echo'd $DISPLAY. Lo, it was 1.0, and the following works fine: > > xterm -display :1.0 & > > Yes, I know it says 1.0 in the tip for the Cygwin/Xserver:1.0 app, but > I didn't actually look at that detail until now, as I'm posting. > > A google for the following doesn't turn up anything: > > cygwin xterm "-display :0.0" "display :1.0" > > I'm wondering if this was a planned change in how X-windows works or > if something is awry with my setup, causing a server with display :0.0 > to fail, and making go to :1.0. I did a browse of the cygin announce > list on gmane (since the X-windows announce list is now obsolete), but > no joy. And I would have expected anything to show up in my google > search. > > Can anyone point me to the description of this change? If it is not a > deliberate change, what would be a good approach to troubleshoot it? > I have a file ~/.xsession-errors, but it is dated 2015-09-16, and I've > used X-windows plenty since then. > Hi, you may have a leftover lock file from a crashed X session. Check if there is a /tmp/.X0-lock (IIRC) before you start your X server. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/