public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Issue with XWin under xlaunch
Date: Mon, 23 Apr 2012 15:04:00 -0000	[thread overview]
Message-ID: <4F956F70.4080900@cornell.edu> (raw)
In-Reply-To: <4F955E58.8060403@dronecode.org.uk>

On 4/23/2012 9:51 AM, Jon TURNEY wrote:
> 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.

Would it be possible for you to also add some code for diagnosing problems with processes started from .startxwinrc?  I'm hoping it might help with the problem I reported in

  http://cygwin.com/ml/cygwin-xfree/2012-04/msg00050.html

BTW, I tried the snapshot at

  ftp://cygwin.com/pub/cygwinx/XWin.20120423-git-638383315ef51e46.exe.bz2

and the resulting log has a lot of messages like this:

 winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter)
 winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes)

Is that to be expected, or does it indicate a real problem?

Ken

--
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/


  reply	other threads:[~2012-04-23 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 10:24 Eliot Moss
2012-04-23 13:51 ` Jon TURNEY
2012-04-23 15:04   ` Ken Brown [this message]
2012-04-24 11:54     ` Jon TURNEY
2012-04-24 13:27       ` Ken Brown
2012-04-23 16:42   ` Eliot Moss
2012-04-23 16:46     ` Eliot Moss
2012-04-24 11:40     ` Jon TURNEY
2012-04-24 12:23       ` Eliot Moss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F956F70.4080900@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).