X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
X-Authority-Reason:	nr=8
X-Authority-Analysis:	v=2.3 cv=NPb7BXyg c=1 sm=1 tr=0
	a=7f+4XAqqJ0zRqjcv4Gsvzg==:117 a=7f+4XAqqJ0zRqjcv4Gsvzg==:17
	a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19
	a=IkcTkHD0fZMA:10:nop_charset_1 a=SS2py6AdgQ4A:10:nop_rcvd_month_year
	a=tsE32L7UpooA:10:endurance_base64_authed_username_1 a=BAdnOv0JORnYES9iOPwA:9
	a=QEXdDO2ut3YA:10:nop_charset_2
DKIM-Signature:	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=astrofoto.org; s=default; h=Content-Transfer-Encoding:Content-Type:
	In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:
	Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:
	Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:
	List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=z37Z9gPdc1na3TXj/yehXv1eekqojFZXGE1QDvLd6kQ=; b=zkf+/M0bV7YvFxZbSsYlo9flcb
	EBXN8pVGqnf1Obo/w/tZ1aOZKzTQd9TRJu4T5GNQsJy6n+hgGssRqJnKjS/z9eVkxb6Y9DNPjGgZs
	QV31M8U0J5PKY6RfSP7dyqqqU5YcumHu1Xf81hsVGN51EjYfeQmy2l/k9K2zVdckJVh0=;
Subject:	Re: Cygwin/X XWinrc menu no longer launches after recent updates
To:	cygwin AT cygwin DOT com
References:	<345b8a7a-bcbb-450b-08c0-943f3bb3b683 AT astrofoto DOT org>
	<20200303185335 DOT 5f4369c163b3a4b241ef429d AT nifty DOT ne DOT jp>
	<f5b1rq9k4wr DOT fsf AT ecclerig DOT inf DOT ed DOT ac DOT uk>
	<20200303213524 DOT 5ddf37854e2eb85eca50ed96 AT nifty DOT ne DOT jp>
	<f5bsgipipce DOT fsf AT ecclerig DOT inf DOT ed DOT ac DOT uk>
	<20200303215912 DOT 6c72af3e17e8ef0f0f58b8a6 AT nifty DOT ne DOT jp>
	<4443035d-133f-99de-285e-d8268c5a8822 AT astrofoto DOT org>
From:	Roland Roberts <roland AT astrofoto DOT org>
Message-ID:	<3367ed10-7403-cf7e-8d4d-e336406f5f8e@astrofoto.org>
Date:	Sat, 7 Mar 2020 21:14:34 -0500
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
	Thunderbird/68.5.0
MIME-Version:	1.0
In-Reply-To:	<4443035d-133f-99de-285e-d8268c5a8822@astrofoto.org>
X-AntiAbuse:	This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse:	Primary Hostname - box925.bluehost.com
X-AntiAbuse:	Original Domain - cygwin.com
X-AntiAbuse:	Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse:	Sender Address Domain - astrofoto.org
X-BWhitelist:	no
X-Source-IP:	104.162.67.78
X-Source-L:	No
X-Exim-ID:	1jAlSe-0043DJ-4V
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender:	cpe-104-162-67-78.nyc.res.rr.com ([192.168.3.18])
	[104.162.67.78]:63494
X-Source-Auth:	roland AT astrofoto DOT org
X-Email-Count:	1
X-Source-Cap:	YXN0cm9mb3Q7YXN0cm9mb3Q7Ym94OTI1LmJsdWVob3N0LmNvbQ==
X-Local-Domain:	yes
X-Spam-Status:	No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	Cygwin mailing list <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<http://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 029IuYrX015979

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
"--Problem reports:       http://cygwin.com/problems.htmlFAQ:                   http://cygwin.com/faq/Documentation:         http://cygwin.com/docs.htmlUnsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple"

- Raw text -