From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gproxy5-pub.mail.unifiedlayer.com (gproxy5-pub.mail.unifiedlayer.com [67.222.38.55]) by server2.sourceware.org (Postfix) with ESMTPS id 34625394202C for ; Sun, 8 Mar 2020 02:14:38 +0000 (GMT) Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy5.mail.unifiedlayer.com (Postfix) with ESMTP id 772BE140A9D for ; Sat, 7 Mar 2020 19:14:36 -0700 (MST) Received: from box925.bluehost.com ([69.195.124.125]) by cmsmtp with ESMTP id AlSejKHQgxD3VAlSejYET7; Sat, 07 Mar 2020 19:14:36 -0700 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=; Received: from cpe-104-162-67-78.nyc.res.rr.com ([104.162.67.78]:63494 helo=[192.168.3.18]) by box925.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from ) id 1jAlSe-0043DJ-4V for cygwin@cygwin.com; Sat, 07 Mar 2020 19:14:36 -0700 Subject: Re: Cygwin/X XWinrc menu no longer launches after recent updates To: cygwin@cygwin.com References: <345b8a7a-bcbb-450b-08c0-943f3bb3b683@astrofoto.org> <20200303185335.5f4369c163b3a4b241ef429d@nifty.ne.jp> <20200303213524.5ddf37854e2eb85eca50ed96@nifty.ne.jp> <20200303215912.6c72af3e17e8ef0f0f58b8a6@nifty.ne.jp> <4443035d-133f-99de-285e-d8268c5a8822@astrofoto.org> From: Roland Roberts 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> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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@astrofoto.org X-Email-Count: 1 X-Source-Cap: YXN0cm9mb3Q7YXN0cm9mb3Q7Ym94OTI1LmJsdWVob3N0LmNvbQ== X-Local-Domain: yes X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_20, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS autolearn=ham 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2020 02:14:39 -0000 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