From: Roland Roberts <roland@astrofoto.org>
To: cygwin@cygwin.com
Subject: Re: Cygwin/X XWinrc menu no longer launches after recent updates
Date: Sat, 7 Mar 2020 21:14:34 -0500 [thread overview]
Message-ID: <3367ed10-7403-cf7e-8d4d-e336406f5f8e@astrofoto.org> (raw)
In-Reply-To: <4443035d-133f-99de-285e-d8268c5a8822@astrofoto.org>
On 3/3/2020 8:12 PM, Roland Roberts wrote:
> On 3/3/2020 7:59 AM, Takashi Yano wrote:
>> On Tue, 03 Mar 2020 12:40:17 +0000
>> "Henry S. Thompson" wrote:
>>> Takashi Yano writes:
>>>> This bug was already fixed in current git head.
>>> Current git head for Cygwin? Or mintty?
>>
>> I mean cygwin.
>>
>>> Because I have another box, and now see that the bug does _not_ occur
>>> with Cygwin 3.1.4 and mintty 3.1.0 -- the above error labelled 3.1.4 is
>>> with Cygwin 3.1.4 _and_ mintty 3.1.4.
>>
>> In my environment, your problem does not occur even with cygwin
>> 3.1.4 and mintty 3.1.4. So I am not sure what is the real cause.
>
> Well, for me it *does* happen with cygwin 3.1.4 and mintty 3.1.4. I
> tried rolling back just mintty to 3.1.0 and it still happened. Then I
> rolled both of them back and it no longer happens, at least on one of my
> systems where I am *not* running sshd. Now to go try the other one....
For me, it is sufficient to roll back just cygwin to 3.1.0. The mintty
version does not matter at all.
roland
prev parent reply other threads:[~2020-03-08 2:14 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
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 [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=3367ed10-7403-cf7e-8d4d-e336406f5f8e@astrofoto.org \
--to=roland@astrofoto.org \
--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).