From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3583 invoked by alias); 1 Dec 2014 20:32:07 -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 3566 invoked by uid 89); 1 Dec 2014 20:32:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: stargate.mehconsulting.com Received: from stargate.mehconsulting.com (HELO stargate.mehconsulting.com) (65.78.188.61) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 01 Dec 2014 20:32:05 +0000 Received: from [192.168.140.48] (vpn.fdielt.com [64.170.21.194]) (authenticated bits=0) by stargate.mehconsulting.com (8.13.8/8.13.8) with ESMTP id sB1KW2wE015574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 1 Dec 2014 12:32:02 -0800 Message-ID: <547CD041.20109@winfirst.com> Date: Mon, 01 Dec 2014 20:32:00 -0000 From: Mark Hansen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: 64-bit xfree86 failing References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2014-12/txt/msg00005.txt.bz2 On 12/1/2014 8:35 AM, Tim Kingman wrote: > 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 > Tim, Are you opposed to having the X Server start when you log into the Windows machine? This is what I do and it works well. The X server is always running when I need it. I created a desktop shortcut with the following command: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/startxwin.exe -- -emulate3buttons 100 -multiwindow -clipboard -swcursor" and then just place that shortcut in the "programs -> startup" start menu folder. -- 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/