From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8043 invoked by alias); 1 Dec 2014 16:35:28 -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 7992 invoked by uid 89); 1 Dec 2014 16:35:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-vc0-f175.google.com Received: from mail-vc0-f175.google.com (HELO mail-vc0-f175.google.com) (209.85.220.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 01 Dec 2014 16:35:26 +0000 Received: by mail-vc0-f175.google.com with SMTP id hy10so4805037vcb.20 for ; Mon, 01 Dec 2014 08:35:24 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.52.244.78 with SMTP id xe14mr24485143vdc.6.1417451724407; Mon, 01 Dec 2014 08:35:24 -0800 (PST) Received: by 10.31.148.78 with HTTP; Mon, 1 Dec 2014 08:35:24 -0800 (PST) Date: Mon, 01 Dec 2014 16:35:00 -0000 Message-ID: Subject: Re: 64-bit xfree86 failing From: Tim Kingman To: cygwin-xfree@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00001.txt.bz2 I see the same issue, and it looks like this is because I have an empty (commented-out) ~/.startxwinrc Removing this file causes X to open and start an xterm, probably because it broke several of the new rules in https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html : * User-defined ~/.startxwinrc files must now be executable, the final command therein must be run in the foreground, and that command's exiting will end the X session, just like with startx and ~/.xinitrc or ~/.Xclients. This causes another problem for me because my .bashrc calls startxwin to make sure I always have an X server running ( per http://stackoverflow.com/a/9301966 ), and then I get caught in a loop of launching new X servers infinitely (probably from startxwin now finding a new DISPLAY, and if I specify both :0 and -silent-dup-error, XWin still writes an error to the console that display 0 is already active, and displays a Windows dialog with an error about not being able to move XWin.0.log to XWin.0.log.old ). I'll keep playing with this to see if I can come up with a solution to duplicate my previous behavior: Any new bash shell makes sure that X is running, with no X apps running, and only one X is running, and new shells don't pop up any "display already exists" errors. Thanks, Tim -- 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/