From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Cygwin/X XWinrc menu no longer launches after recent updates
Date: Tue, 03 Mar 2020 09:53:00 -0000 [thread overview]
Message-ID: <20200303185335.5f4369c163b3a4b241ef429d@nifty.ne.jp> (raw)
In-Reply-To: <345b8a7a-bcbb-450b-08c0-943f3bb3b683@astrofoto.org>
On Tue, 3 Mar 2020 00:14:12 -0500
Roland Roberts wrote:
> I only noticed this in the last week or so, and assumed I'd messed up
> something with Windows 10 permission, which is still a possibility. My
> first attempt to "fix" this was to reinstall pretty much everything in
> Cygwin that was part of X11 or Base. And that seemed to fix
> things...until I rebooted Windows.
>
> There are no errors in the logs, not stackdumps, nothign to indicate
> anything is not working. The X log is below. You'll notice it says
>
> "executing '/bin/mintty', pid 3152"
>
> but that window never opens. If I start a shell directly via my desktop
> shortcut, which has this as it's target
>
> C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico -
>
> I can see that there is no PID 3152.
Does reverting cygwin1.dll to 3.1.2 help?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-03-03 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 5:14 Roland Roberts
2020-03-03 9:53 ` Takashi Yano [this message]
2020-03-03 12:18 ` Henry S. Thompson
2020-03-03 12:35 ` Takashi Yano
2020-03-03 12:40 ` Henry S. Thompson
2020-03-03 12:59 ` Takashi Yano
2020-03-03 21:43 ` Henry S. Thompson
2020-03-03 22:20 ` Brian Inglis
2020-03-03 23:25 ` Brian Inglis
2020-03-04 1:12 ` Henry S. Thompson
2020-03-03 23:46 ` Henry S. Thompson
2020-03-04 19:05 ` Brian Inglis
2020-03-04 19:05 ` Henry S. Thompson
2020-03-04 8:59 ` Roland Roberts
2020-03-08 2:14 ` Roland Roberts
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=20200303185335.5f4369c163b3a4b241ef429d@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@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).