From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23785 invoked by alias); 23 Apr 2012 13:51:35 -0000 Received: (qmail 23756 invoked by uid 22791); 23 Apr 2012 13:51:33 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,TW_TX X-Spam-Check-By: sourceware.org Received: from smtpout.karoo.kcom.com (HELO smtpout.karoo.kcom.com) (212.50.160.34) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Apr 2012 13:51:20 +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; 23 Apr 2012 14:51:19 +0100 Message-ID: <4F955E58.8060403@dronecode.org.uk> Date: Mon, 23 Apr 2012 13:51: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> In-Reply-To: <4F855BAC.7010809@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/msg00079.txt.bz2 On 11/04/2012 11:23, Eliot Moss wrote: > When I start XWin using xlaunch, trying to the start > programs from the .XWinrc popup menu (right-click on > the X icon, left-click on the program's entry in the > menu), programs do not start. I get only those programs > started by my script that I told xlaunch to run. > > I would like to use xlaunch, since it solves the issue > I had with the startxwin taskbar icon being visible > (when I claim it should not be, and it didn't use to > be), but not being able to start additional programs > makes this approach less useable. > > Looking at this from outside, it is hard to say whether > the real issue is in xlaunch, in XWin, or the result of > some misunderstanding between them. At the moment, the output from processes started from the notification area icon doesn't go anywhere useful, which can make it hard to debug problems with processes started this way. I've added some code to capture stdout and stderr from these subprocesses to the X server log, and to more clearly diagnose problems which could occur while fork/exec-ing them. Perhaps you could try the snapshot at [1] and see if this gives a bit more information about why these processes are failing? [1] ftp://cygwin.com/pub/cygwinx/XWin.20120423-git-638383315ef51e46.exe.bz2 -- 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/