From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17851 invoked by alias); 30 Mar 2015 14:17:34 -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 17838 invoked by uid 89); 30 Mar 2015 14:17:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: out2-smtp.messagingengine.com Received: from out2-smtp.messagingengine.com (HELO out2-smtp.messagingengine.com) (66.111.4.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 30 Mar 2015 14:17:33 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2602B20A91 for ; Mon, 30 Mar 2015 10:17:28 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 30 Mar 2015 10:17:31 -0400 Received: from [192.168.1.102] (unknown [31.51.205.126]) by mail.messagingengine.com (Postfix) with ESMTPA id C8E05680180; Mon, 30 Mar 2015 10:17:30 -0400 (EDT) Message-ID: <55195AF7.9070706@dronecode.org.uk> Date: Mon, 30 Mar 2015 14:35:00 -0000 From: Jon TURNEY Reply-To: cygwin@cygwin.com User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Jim Reisert AD1C , cygwin@cygwin.com Subject: Re: Xorg server always starting up on DISPLAY 3.0 References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2015-03/txt/msg00521.txt.bz2 On 27/03/2015 15:48, Jim Reisert AD1C wrote: > I'm running Cygwin/X server Version 1.17.1. For the last couple of > weeks, it's always starting on DISPLAY 3.0: > > DISPLAY=:3.0 > > I can't figure out how to get it back to 0.0. There must be some > piece of state somewhere that I can't find. You have stale lock files /tmp/.X0-lock etc. Unfortunately startx(|win) is not as smart as it should be about detecting that the process owning the lock file is no longer running. -- 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