From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19731 invoked by alias); 16 Dec 2014 03:30: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 19694 invoked by uid 89); 16 Dec 2014 03:30:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_00,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: plane.gmane.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 16 Dec 2014 03:30:37 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Y0iqH-0005o8-4J for cygwin-xfree@cygwin.com; Tue, 16 Dec 2014 04:30:33 +0100 Received: from 65.75.36.70 ([65.75.36.70]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Dec 2014 04:30:33 +0100 Received: from gyliamos by 65.75.36.70 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Dec 2014 04:30:33 +0100 To: cygwin-xfree@cygwin.com From: Will Parsons Subject: Re: startxwin.exe no longer exists? Date: Tue, 16 Dec 2014 03:30:00 -0000 Message-ID: References: <548C82A3.9080604@gmail.com> <548F9F4B.6050002@cygwin.com> Reply-To: gyliamos@gmail.com User-Agent: slrn/1.0.1 (FreeBSD) X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00034.txt.bz2 Larry Hall (Cygwin-X) wrote: > On 12/15/2014 09:49 PM, Will Parsons wrote: >> Marco Atzeri wrote: >>> >>> On 12/12/2014 7:07 PM, Will Parsons wrote: >>>> For several years now I have been starting X windows by clicking on an >>>> icon on my desktop that is a link to C:\cygwin\bin\startxwin.exe. It >>>> has recently ceased to work because apparently startxwin.exe no longer >>>> exists. Somehow I missed where this was removed, so what is the >>>> recommended way of starting X from a desktop icon now? >>>> >>>> I seem to recall that startxwin.exe was introduced some time ago >>>> because using a script to start X was inadequate somehow, but I don't >>>> remember the details, so what changed? >>>> >>> https://cygwin.com/ml/cygwin-xfree-announce/2014-11/msg00004.html >> >> OK - so what I get from that is that whatever problems were associated >> with the original shell script have been solved and startxwin is now a >> shell script again. But, my basic question is unanswered - how do I >> start an X session from an icon? Obviously, simply replacing the link >> to startxwin.exe to startxwin will not work, so I copied the shortcut >> from the start menu to the desktop and tried it (after renaming my >> .xinitrc and .startxwinrc files to avoid any problems with the change >> of model). >> >> If I click on the icon, I *do* get an X session (along with an xterm >> that I don't need), but if try (e.g.) to start emacs under mintty, I >> get a non-X emacs, with an error message: >> >> Display :0 unavailable, simulating -nw >> >> Sure, display :0 is unavailable; checking DISPLAY in the (unwanted) >> xterm shows DISPLAY is set to :5. Why's that I wonder? >> >> Further investigation shows ls -ltr /tmp: >> >> -r--r--r-- 1 william None 11 Nov 28 17:43 /tmp/.X0-lock >> -r--r--r-- 1 william None 11 Dec 13 17:43 /tmp/.X1-lock >> -r--r--r-- 1 william None 11 Dec 13 17:55 /tmp/.X2-lock >> -r--r--r-- 1 william None 11 Dec 13 19:22 /tmp/.X3-lock >> -r--r--r-- 1 william None 11 Dec 15 16:53 /tmp/.X4-lock >> -r--r--r-- 1 william None 11 Dec 15 17:00 /tmp/.X5-lock >> >> Interesting. It looks like every time I start an X session a lock >> file is created and doesn't get deleted, so the display number keeps >> changing. This doesn't look right, so how do I avoid it? > > You will get one lock file for every instance of the server you are running. > To remove the lock files, kill all instances of the server and remove any > remaining lock files. Then you can start a single session. well, I *had* killed them. Are you saying I need to manually remove these old lock files? I suppose I can come up with a way of semi-automating this, but it doesn't seem like it should be necessary. Is this a matter of X sessions not properly exiting? -- Will -- 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/