From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17221 invoked by alias); 24 Apr 2012 11:40:29 -0000 Received: (qmail 17055 invoked by uid 22791); 24 Apr 2012 11:40:27 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from mercury.karoo.kcom.com (HELO smtpout.karoo.kcom.com) (212.50.160.61) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Apr 2012 11:40:10 +0000 Received: from 213-152-38-55.dsl.eclipse.net.uk (HELO [192.168.1.105]) ([213.152.38.55]) by smtpout.karoo.kcom.com with ESMTP; 24 Apr 2012 12:40:09 +0100 Message-ID: <4F96911C.30608@dronecode.org.uk> Date: Tue, 24 Apr 2012 11:40:00 -0000 From: Jon TURNEY Reply-To: cygwin-xfree User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: moss@cs.umass.edu Subject: Re: Issue with XWin under xlaunch References: <4F855BAC.7010809@cs.umass.edu> <4F955E58.8060403@dronecode.org.uk> <4F95864B.1090802@cs.umass.edu> In-Reply-To: <4F95864B.1090802@cs.umass.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 X-SW-Source: 2012-04/txt/msg00085.txt.bz2 On 23/04/2012 17:41, Eliot Moss wrote: > Ok -- by perusing the log I figured it out ... > [727848.279] executing 'xterm -display :0.0 -ls -title swarm -bg rgbi:.0/.20/.0 -geometry 120x47+0+0 -e /usr/bin/ssh moss@swarm.cs.umass.edu', pid 13748 > [727848.311] (pid 13748 stderr) /bin/sh: xterm: command not found > In the past, .XWinrc names of files such as "xterm" > worked just fine. Apparently something changed about > the PATH used, and "xterm" was not being found. When > I write /usr/bin/xterm, it starts up. You can see the > first case and the second in the attached log file. > > So, I think xlaunch is ok, but this was a surprising > difference :-) ... This is not intentional. I can't reproduce this, so I'm not quite sure what is causing this. What I am expecting to happen is that xlaunch is invoked via the start menu shortcut which it's package creates, which runs bash -l -c xlaunch, which reads /etc/profile, which sets PATH to include /usr/bin, which should be inherited by XWin and used when it execs /bin/sh -c 'your xterm command'. We try to create the login environment as far up the process hierarchy as possible, rather than starting the processes from the notification area menu with bash -l -c, as creating the login environment can be expensive. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/