This is the mail archive of the
mailing list for the Cygwin XFree86 project.
Re: Issue with XWin under xlaunch
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-xfree at cygwin dot com
- Cc: moss at cs dot umass dot edu
- Date: Mon, 23 Apr 2012 14:51:20 +0100
- Subject: Re: Issue with XWin under xlaunch
- References: <4F855BAC.email@example.com>
- Reply-to: cygwin-xfree <cygwin-xfree at cygwin dot com>
- Reply-to: cygwin-xfree at cygwin dot com
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  and see if this gives a bit more
information about why these processes are failing?
Volunteer Cygwin/X X Server maintainer
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html