X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 1 Jun 2012 20:16:26 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Mintty Log Off problem (now 1.7.16s) Message-ID: <20120601181626.GE28506@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4FC8F950 DOT 2000605 AT w5pny DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4FC8F950.2000605@w5pny.com> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jun 1 11:18, Harry G McGavran Jr wrote: > > >On May 30 14:16, Harry G McGavran Jr wrote: > >> Corinna wrote: > >> > >> >That's why I'm asking. If you could try to find out which snapshot > >> >fixed it and which snapshot broke it again, it would help to find the > >> >cause. > >> > > >> > > >> >Thanks, > >> >Corinna > >> > >> This will take a little time since one has to log off to see the problem > >> and I have no idea which 1.7.10s was the starting point. Unfortunately, > >> the rest of this week, I won't have very much time to do many > >> iterations. I'll see if I can find where it started and post back, > >> but unless it's in the first few tries, it will likely be sometime > >> next week before I have the answer... > > > >No worries. Next week is fine. > > > > > >Corinna > > > >-- > >Corinna Vinschen Please, send mails regarding Cygwin to > >Cygwin Project Co-Leader cygwin AT cygwin DOT com > >Red Hat > > > > > > Today I had a just enought time to try the first 1.7.10s snapshot I > could find on the cygwin snapshots webpage. That was > cygwin-inst-20111217.tar.bz2, and the problem does exist with that snapshot. > I don't know if there were any earlier ones prior to that but > after 1.7.9 or not since the chart on the webpage starts with > that snapshot. That's not very helpful, unfortunately. You reported in Feb or Mar that one of the snapshots fixed the problem for you. And you reported that it's now in May broken again. So there's one snapshot in the list which was the first one which fixed it, and there's another snapshot in the list which is the first one which broke it again. If we know which snapshots that are, we're a big step further to fix this problem again. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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