From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 905 invoked by alias); 4 Jul 2017 17:57:49 -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 849 invoked by uid 89); 4 Jul 2017 17:57:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Dept, H*UA:version, H*x:version, Centre X-HELO: cliff.scrc.umanitoba.ca Received: from cliff.scrc.umanitoba.ca (HELO cliff.scrc.umanitoba.ca) (140.193.42.125) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 04 Jul 2017 17:57:46 +0000 Received: from cliff.scrc.umanitoba.ca (loopback [127.0.0.1]) by cliff.scrc.umanitoba.ca (8.14.7/8.14.7) with ESMTP id v64HvhOZ031767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 4 Jul 2017 12:57:43 -0500 Received: (from grdetil@localhost) by cliff.scrc.umanitoba.ca (8.14.7/8.13.8/Submit) id v64Hvh5n031763; Tue, 4 Jul 2017 12:57:43 -0500 From: Gilles Detillieux Message-Id: <201707041757.v64Hvh5n031763@cliff.scrc.umanitoba.ca> Subject: XWin Server doesn't start reliably under Windows 10 Creator's Update To: cygwin@cygwin.com Date: Tue, 04 Jul 2017 17:57:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2017-07/txt/msg00050.txt.bz2 A few people on this list have reported problems with XWin Server not starting reliably from the Start menu, particularly after recent updates. I've found this too, and I think I have a reasonable fix for it. There seems to be an incompatibility with recent versions of the XWin server launcher shortcut and Windows 10 Creator's Update. What seems to be happening is that the launcher doesn't wait for the server to start, and when the launcher exits the server dies before it has a chance to get itself running properly. Nothing gets logged when it fails, which makes it tricky to diagnose this problem when it happens (which is frequently!). I found a few tweaks to the shortcut target script to keep run.exe from exiting prematurely and killing the server. The trick is to find the launcher shortcut and make two simple changes to the one-line script in the shortcut's target. Click on Windows 10's start menu, navigate to the Cygwin-X folder, click on it, then right-click on the "XWin Server" icon, select "More...", and click on "Open file location". In the folder that opens, right-click on the "XWin Server" icon in there, and select "Properties". In the Properties window, find the Target field. It should have the command line: C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec /usr/bin/startxwin" Change it to: C:\cygwin\bin\run.exe --wait --quote /usr/bin/bash.exe -l -c "cd; exec /usr/bin/startxwin &" i.e. add the --wait option to the run.exe command, and add the "&" sign to the end of the startxwin command. This changes the stage at which startxwin goes into the background, and seems to work reliably under Creator's Update. Ultimately, this may be down to a problem with how run.exe works (or doesn't) under recent Windows 10 systems, but this workaround has worked for me. When you save this change, Windows will require admin. privileges, which is easy if you have an admin. account, but I expect with a limited account you'll just have to provide the username & password for an admin. user. If you also have a Desktop icon for XWin Server, change it the same way, by right-clicking on the icon and selecting Properties. Finally, if you also pinned the icon to the taskbar, you can just unpin it and re-pin it from the updated Start menu entry. Hopefully the maintainers can find a more permanent solution to this, or at least implement this tweak in the xorg-server package. -- Gilles Detillieux Spinal Cord Research Centre Dept. of Physiology and Pathophysiology, Rady Faculty of Health Sciences, Univ. of Manitoba, Winnipeg, MB -- 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