public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Roland Roberts <roland@astrofoto.org>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Cygwin/X on Windows 10 won't launch apps from .XWinrc menus
Date: Mon, 23 Aug 2021 08:46:24 -0400	[thread overview]
Message-ID: <8723609c-4a10-a4fd-47f7-5f4fb3c8ae48@astrofoto.org> (raw)
In-Reply-To: <b13207ee-740f-f90a-21bb-0ca29efbc471@dronecode.org.uk>

On 8/21/2021 10:49 AM, Jon Turney wrote:
> On 10/08/2021 13:58, Roland Roberts wrote:
>> I have a new, company-supplied Windows 10 laptop, using Cygwin to do 
>> development. I’m having a problem getting XWin to launch apps. XWin 
>> appears to be mostly working normally, meaning if I launch a Cygwin 
>> mintty instance, I can manually set DISPLAY=:0.0 and start up X 
>> application from the shell prompt. But trying to launch from my 
>> .XWinrc, the application never displays and I can’t find a useful 
>> error log to track down the issue. I’m pretty sure it’s some 
>> permission someplace my account doesn’t have (and I can probably get 
>> IT to change that if I can just identify what it is).
>
> I'm not sure what the evidence for this hypothesis is?

You're right, it was a complete guess since that's been where most of my 
problems have been with the new machine.


> [...]
> The process being created, but not changing command is usually 
> symptomatic of problems with cygwin's fork emulation (i.e. the child 
> process gets stuck during the complex synchronization it does with the 
> parent, before exec gets called)
>
>> Any suggestions on where to poke to diagnose this? My home Windows 10 
>> machine has no problem at all. Oh, and cygcheck report version 3.1.4. 
>> Yes, that’s a little old, but we are stuck there until we can work 
>> out an issue with our build environment and the change for 3.1.5+ in 
>> how symlinks are handled.
>
> There are some suggestions about dealing with fork problems in the 
> FAQ, but sometimes nothing works and we don't know why.

Thanks, I'll look through those suggestions. I'm still trying to figure 
out what the key difference in my two environments is that on Windows 10 
machine works fine for this and the other doesn't. And the one where it 
doesn't, it only doesn't work when launched from the XWinrc menu, it 
works fine when launched from mintty.

roland


-- 
Roland Roberts, PhD
Brooklyn, NY USA
https://astrofoto.org


      reply	other threads:[~2021-08-23 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 12:58 Roland Roberts
2021-08-18 23:19 ` Roland Roberts
2021-08-19 18:41   ` Eliot Moss
2021-08-19 22:22     ` Roland Roberts
2021-08-21 14:49 ` Jon Turney
2021-08-23 12:46   ` Roland Roberts [this message]

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=8723609c-4a10-a4fd-47f7-5f4fb3c8ae48@astrofoto.org \
    --to=roland@astrofoto.org \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).