Mintty Log Off problem

Mintty Log Off problem

[Harry G McGavran Jr]

With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
with a "End Now" and "Cancel" button every time I log off
Windows and I have somewhere in that Windows session run
the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
in it and my default shell is tcsh.  This never happened
with previous Cygwin releases.  What's even more interesting
is that in all cases I exit all my programs before logging
off, including the mintty window.  I've even tried hitting
the "Cancel" button and then looking for a process named
mintty or "Terminal" (since that's what mintty's description
is and that is used by some process tools) with both Process Explorer
and Task Manager, but I can find no such process -- and then
when I try to log off again not having found such a process
the pop-up comes back and I can't log off until I hit
"End Now".

Since I haven't seen any reports of this on this list, I must
be about the only one this is happening to.  Any clues as to
what I can do to find out what Windows is actually failing to stop
when I try to log off having run mintty beforehand?
-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem

[Harry G McGavran Jr]

I've found a little more information -- this problem goes away
if I change my default shell to dash.  Seems tcsh is involved somehow.
It comes back when I change my default shell back to tcsh.
Going back to tcsh 6.18.00-2 does not help.

Given the deathly silence to my request below, I must be the only
one experiencing this, but it happens on both of my machines.

     Harry

On 02/15/12 10:43, Harry G McGavran Jr wrote:
> With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
> I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
> with a "End Now" and "Cancel" button every time I log off
> Windows and I have somewhere in that Windows session run
> the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
> in it and my default shell is tcsh. This never happened
> with previous Cygwin releases. What's even more interesting
> is that in all cases I exit all my programs before logging
> off, including the mintty window. I've even tried hitting
> the "Cancel" button and then looking for a process named
> mintty or "Terminal" (since that's what mintty's description
> is and that is used by some process tools) with both Process Explorer
> and Task Manager, but I can find no such process -- and then
> when I try to log off again not having found such a process
> the pop-up comes back and I can't log off until I hit
> "End Now".
>
> Since I haven't seen any reports of this on this list, I must
> be about the only one this is happening to. Any clues as to
> what I can do to find out what Windows is actually failing to stop
> when I try to log off having run mintty beforehand?

-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem

[David Rothenberger]

On 2/18/2012 10:28 AM, Harry G McGavran Jr wrote:
> I've found a little more information -- this problem goes away
> if I change my default shell to dash.  Seems tcsh is involved somehow.
> It comes back when I change my default shell back to tcsh.
> Going back to tcsh 6.18.00-2 does not help.
> 
> Given the deathly silence to my request below, I must be the only
> one experiencing this, but it happens on both of my machines.

I'm also experiencing this on my XP SP3 machines using mintty and bash.
No problems on Vista or W7, though.

> On 02/15/12 10:43, Harry G McGavran Jr wrote:
>> With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
>> I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
>> with a "End Now" and "Cancel" button every time I log off
>> Windows and I have somewhere in that Windows session run
>> the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
>> in it and my default shell is tcsh. This never happened
>> with previous Cygwin releases. What's even more interesting
>> is that in all cases I exit all my programs before logging
>> off, including the mintty window. I've even tried hitting
>> the "Cancel" button and then looking for a process named
>> mintty or "Terminal" (since that's what mintty's description
>> is and that is used by some process tools) with both Process Explorer
>> and Task Manager, but I can find no such process -- and then
>> when I try to log off again not having found such a process
>> the pop-up comes back and I can't log off until I hit
>> "End Now".
>>
>> Since I haven't seen any reports of this on this list, I must
>> be about the only one this is happening to. Any clues as to
>> what I can do to find out what Windows is actually failing to stop
>> when I try to log off having run mintty beforehand?
> 


-- 
David Rothenberger  ----  daveroth@acm.org

Pickle's Law:
        If Congress must do a painful thing,
        the thing must be done in an odd-number year.

--
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

Re: Mintty Log Off problem

[Gary Johnson]

On 2012-02-18, David Rothenberger wrote:
> On 2/18/2012 10:28 AM, Harry G McGavran Jr wrote:
> > I've found a little more information -- this problem goes away
> > if I change my default shell to dash.  Seems tcsh is involved somehow.
> > It comes back when I change my default shell back to tcsh.
> > Going back to tcsh 6.18.00-2 does not help.
> > 
> > Given the deathly silence to my request below, I must be the only
> > one experiencing this, but it happens on both of my machines.
> 
> I'm also experiencing this on my XP SP3 machines using mintty and bash.
> No problems on Vista or W7, though.

I see this occasionally, too, using XP, mintty and bash.  It doesn't
seem to happen every time I reboot.  It hasn't been annoying enough,
and I don't reboot often enough, for me to have determined a
pattern.

Regards,
Gary


--
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

Re: Mintty Log Off problem

[Earnie Boyd]

On Sat, Feb 18, 2012 at 1:28 PM, Harry G McGavran Jr wrote:
> I've found a little more information -- this problem goes away
> if I change my default shell to dash.  Seems tcsh is involved somehow.
> It comes back when I change my default shell back to tcsh.
> Going back to tcsh 6.18.00-2 does not help.
>
> Given the deathly silence to my request below, I must be the only
> one experiencing this, but it happens on both of my machines.

The common response to you and the others who responded with "me too"
for this issue is to check the latest snapshot and report if it still
occurs.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

--
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

Re: Mintty Log Off problem

[Harry G McGavran Jr]

Earnie Boyd wrote:

>The common response to you and the others who responded with "me too"
>for this issue is to check the latest snapshot and report if it still
>occurs.
>
>--
>Earnie
>

I tried the latest snapshot and the problem didn't occur with
it after having tried running mintty and logging out several times.

Not conclusive proof, but it looks like with the snapshot up
today that the problem does not occur.

     Harry

--

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

On 02/18/12 11:28, Harry G McGavran Jr wrote:
> I've found a little more information -- this problem goes away
> if I change my default shell to dash.  Seems tcsh is involved somehow.
> It comes back when I change my default shell back to tcsh.
> Going back to tcsh 6.18.00-2 does not help.
> 
> Given the deathly silence to my request below, I must be the only
> one experiencing this, but it happens on both of my machines.
> 
>     Harry
> 
> On 02/15/12 10:43, Harry G McGavran Jr wrote:
>> With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
>> I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
>> with a "End Now" and "Cancel" button every time I log off
>> Windows and I have somewhere in that Windows session run
>> the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
>> in it and my default shell is tcsh. This never happened
>> with previous Cygwin releases. What's even more interesting
>> is that in all cases I exit all my programs before logging
>> off, including the mintty window. I've even tried hitting
>> the "Cancel" button and then looking for a process named
>> mintty or "Terminal" (since that's what mintty's description
>> is and that is used by some process tools) with both Process Explorer
>> and Task Manager, but I can find no such process -- and then
>> when I try to log off again not having found such a process
>> the pop-up comes back and I can't log off until I hit
>> "End Now".
>>
>> Since I haven't seen any reports of this on this list, I must
>> be about the only one this is happening to. Any clues as to
>> what I can do to find out what Windows is actually failing to stop
>> when I try to log off having run mintty beforehand?
> 

I'm puzzled why others aren't seeing this or aren't reporting it,
but this problem seems to be back with 1.7.15 and I've now tried
the latest snapshot (May 25) and it's back there too. It occurred
with 1.7.10 and then got fixed, but now it seems to be back.

  Harry

-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

On 05/28/12 11:32, Harry G McGavran Jr wrote:
> 
> 

> 
> I'm puzzled why others aren't seeing this or aren't reporting it,
> but this problem seems to be back with 1.7.15 and I've now tried
> the latest snapshot (May 25) and it's back there too. It occurred
> with 1.7.10 and then got fixed, but now it seems to be back.
> 
>   Harry
> 

It seems this happens at least when I try to log off after I've run a
cygwin X application from mintty, whereas with 1.7.10 it happened
all the time.

   Harry

-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Ryan Johnson]

On 28/05/2012 1:32 PM, Harry G McGavran Jr wrote:
>
> On 02/18/12 11:28, Harry G McGavran Jr wrote:
>> I've found a little more information -- this problem goes away
>> if I change my default shell to dash.  Seems tcsh is involved somehow.
>> It comes back when I change my default shell back to tcsh.
>> Going back to tcsh 6.18.00-2 does not help.
>>
>> Given the deathly silence to my request below, I must be the only
>> one experiencing this, but it happens on both of my machines.
>>
>>      Harry
>>
>> On 02/15/12 10:43, Harry G McGavran Jr wrote:
>>> With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
>>> I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
>>> with a "End Now" and "Cancel" button every time I log off
>>> Windows and I have somewhere in that Windows session run
>>> the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
>>> in it and my default shell is tcsh. This never happened
>>> with previous Cygwin releases. What's even more interesting
>>> is that in all cases I exit all my programs before logging
>>> off, including the mintty window. I've even tried hitting
>>> the "Cancel" button and then looking for a process named
>>> mintty or "Terminal" (since that's what mintty's description
>>> is and that is used by some process tools) with both Process Explorer
>>> and Task Manager, but I can find no such process -- and then
>>> when I try to log off again not having found such a process
>>> the pop-up comes back and I can't log off until I hit
>>> "End Now".
>>>
>>> Since I haven't seen any reports of this on this list, I must
>>> be about the only one this is happening to. Any clues as to
>>> what I can do to find out what Windows is actually failing to stop
>>> when I try to log off having run mintty beforehand?
> I'm puzzled why others aren't seeing this or aren't reporting it,
> but this problem seems to be back with 1.7.15 and I've now tried
> the latest snapshot (May 25) and it's back there too. It occurred
> with 1.7.10 and then got fixed, but now it seems to be back.
I routinely encounter mintty windows that don't close after I exit the 
login shell they run (even though they contain no visible child 
processes), but they can still be closed using the big red "X" in the 
corner... your problem sounds like something more sinister.

Ryan


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Andy Koppe]

On 29 May 2012 13:57, Ryan Johnson wrote:
> On 28/05/2012 1:32 PM, Harry G McGavran Jr wrote:
>>
>>
>> On 02/18/12 11:28, Harry G McGavran Jr wrote:
>>>
>>> I've found a little more information -- this problem goes away
>>> if I change my default shell to dash.  Seems tcsh is involved somehow.
>>> It comes back when I change my default shell back to tcsh.
>>> Going back to tcsh 6.18.00-2 does not help.
>>>
>>> Given the deathly silence to my request below, I must be the only
>>> one experiencing this, but it happens on both of my machines.
>>>
>>>     Harry
>>>
>>> On 02/15/12 10:43, Harry G McGavran Jr wrote:
>>>>
>>>> With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
>>>> I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
>>>> with a "End Now" and "Cancel" button every time I log off
>>>> Windows and I have somewhere in that Windows session run
>>>> the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
>>>> in it and my default shell is tcsh. This never happened
>>>> with previous Cygwin releases. What's even more interesting
>>>> is that in all cases I exit all my programs before logging
>>>> off, including the mintty window. I've even tried hitting
>>>> the "Cancel" button and then looking for a process named
>>>> mintty or "Terminal" (since that's what mintty's description
>>>> is and that is used by some process tools) with both Process Explorer
>>>> and Task Manager, but I can find no such process -- and then
>>>> when I try to log off again not having found such a process
>>>> the pop-up comes back and I can't log off until I hit
>>>> "End Now".
>>>>
>>>> Since I haven't seen any reports of this on this list, I must
>>>> be about the only one this is happening to. Any clues as to
>>>> what I can do to find out what Windows is actually failing to stop
>>>> when I try to log off having run mintty beforehand?
>>
>> I'm puzzled why others aren't seeing this or aren't reporting it,
>> but this problem seems to be back with 1.7.15 and I've now tried
>> the latest snapshot (May 25) and it's back there too. It occurred
>> with 1.7.10 and then got fixed, but now it seems to be back.
>
> I routinely encounter mintty windows that don't close after I exit the login
> shell they run (even though they contain no visible child processes), but
> they can still be closed using the big red "X" in the corner...

Mintty closes when it gets an EOF from the underlying pseudo terminal
device. This happens when there are no more processes connected to it.
The Cygwin console behaves similarly, but other terminal emulators do
not: they close once the direct child process exits no matter whether
other processes are still connected.

Backgrounding a process with '&' or nohupping it doesn't break that
connection, but invoking it through the 'setsid' utility from the
util-linux package does.

See also http://code.google.com/p/mintty/issues/detail?id=319.

Andy

--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Ryan Johnson]

On 29/05/2012 2:27 PM, Andy Koppe wrote:
> On 29 May 2012 13:57, Ryan Johnson wrote:
>> On 28/05/2012 1:32 PM, Harry G McGavran Jr wrote:
>>>
>>> On 02/18/12 11:28, Harry G McGavran Jr wrote:
>>>> I've found a little more information -- this problem goes away
>>>> if I change my default shell to dash.  Seems tcsh is involved somehow.
>>>> It comes back when I change my default shell back to tcsh.
>>>> Going back to tcsh 6.18.00-2 does not help.
>>>>
>>>> Given the deathly silence to my request below, I must be the only
>>>> one experiencing this, but it happens on both of my machines.
>>>>
>>>>      Harry
>>>>
>>>> On 02/15/12 10:43, Harry G McGavran Jr wrote:
>>>>> With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
>>>>> I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
>>>>> with a "End Now" and "Cancel" button every time I log off
>>>>> Windows and I have somewhere in that Windows session run
>>>>> the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
>>>>> in it and my default shell is tcsh. This never happened
>>>>> with previous Cygwin releases. What's even more interesting
>>>>> is that in all cases I exit all my programs before logging
>>>>> off, including the mintty window. I've even tried hitting
>>>>> the "Cancel" button and then looking for a process named
>>>>> mintty or "Terminal" (since that's what mintty's description
>>>>> is and that is used by some process tools) with both Process Explorer
>>>>> and Task Manager, but I can find no such process -- and then
>>>>> when I try to log off again not having found such a process
>>>>> the pop-up comes back and I can't log off until I hit
>>>>> "End Now".
>>>>>
>>>>> Since I haven't seen any reports of this on this list, I must
>>>>> be about the only one this is happening to. Any clues as to
>>>>> what I can do to find out what Windows is actually failing to stop
>>>>> when I try to log off having run mintty beforehand?
>>> I'm puzzled why others aren't seeing this or aren't reporting it,
>>> but this problem seems to be back with 1.7.15 and I've now tried
>>> the latest snapshot (May 25) and it's back there too. It occurred
>>> with 1.7.10 and then got fixed, but now it seems to be back.
>> I routinely encounter mintty windows that don't close after I exit the login
>> shell they run (even though they contain no visible child processes), but
>> they can still be closed using the big red "X" in the corner...
> Mintty closes when it gets an EOF from the underlying pseudo terminal
> device. This happens when there are no more processes connected to it.
> The Cygwin console behaves similarly, but other terminal emulators do
> not: they close once the direct child process exits no matter whether
> other processes are still connected.
>
> Backgrounding a process with '&' or nohupping it doesn't break that
> connection, but invoking it through the 'setsid' utility from the
> util-linux package does.
That's about what I figured, which is why I'd never worried before. 
Although I will say I've sometimes had trouble figuring out what cygwin 
process might be keeping the mintty alive...

Ryan

--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

Ryan Johnson wrote:
>
>I routinely encounter mintty windows that don't close after
>I exit the login shell they run (even though they contain no
>visible child processes), but they can still be closed using
>the big red "X" in the corner... your problem sounds like
>something more sinister.
>
>Ryan
>

There is never an "X" to deal with here.  One never know there is
a problem until he does start->Log Off to log out of windows.

I can normally close any/all mintty windows and then with various
process explorers try to find a mintty process and never find any.
Then when I log out of Windows, Windows claims it has to close
mintty.exe.  This was fixed once in a snapshot of 1.7.10, but
has since returned with 1.7.15.  In this incarnation it seems to
occur whenever I've run a Cygwin X app from a mintty window.
If I've signed on in Windows and never run a Cygwin X app it
generally doesn't happen, but I can't be sure it never happens.
Every time I've run a Cygwin X app though I can expect to see
it after closing (apparently normally) all mintty windows and
then log off of Windows.

    Harry



-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Andy Koppe]

On 29 May 2012 17:17, Harry G McGavran Jr wrote:
>
> Ryan Johnson wrote:
>>
>>I routinely encounter mintty windows that don't close after
>>I exit the login shell they run (even though they contain no
>>visible child processes), but they can still be closed using
>>the big red "X" in the corner... your problem sounds like
>>something more sinister.
>>
>>Ryan
>>
>
> There is never an "X" to deal with here.  One never know there is
> a problem until he does start->Log Off to log out of windows.
>
> I can normally close any/all mintty windows and then with various
> process explorers try to find a mintty process and never find any.
> Then when I log out of Windows, Windows claims it has to close
> mintty.exe.  This was fixed once in a snapshot of 1.7.10, but
> has since returned with 1.7.15.  In this incarnation it seems to
> occur whenever I've run a Cygwin X app from a mintty window.
> If I've signed on in Windows and never run a Cygwin X app it
> generally doesn't happen, but I can't be sure it never happens.
> Every time I've run a Cygwin X app though I can expect to see
> it after closing (apparently normally) all mintty windows and
> then log off of Windows.

Do I understand you correctly that you no longer have any mintty
windows open when this happens? That's puzzling indeed. Have you
looked at ye olde Big List Of Dodgy Applications?

http://cygwin.com/faq/faq.using.html#faq.using.bloda

Andy

--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

On 05/29/12 12:31, Andy Koppe wrote:
> On 29 May 2012 17:17, Harry G McGavran Jr wrote:
>>
>> Ryan Johnson wrote:
>>>
>>> I routinely encounter mintty windows that don't close after
>>> I exit the login shell they run (even though they contain no
>>> visible child processes), but they can still be closed using
>>> the big red "X" in the corner... your problem sounds like
>>> something more sinister.
>>>
>>> Ryan
>>>
>>
>> There is never an "X" to deal with here.  One never know there is
>> a problem until he does start->Log Off to log out of windows.
>>
>> I can normally close any/all mintty windows and then with various
>> process explorers try to find a mintty process and never find any.
>> Then when I log out of Windows, Windows claims it has to close
>> mintty.exe.  This was fixed once in a snapshot of 1.7.10, but
>> has since returned with 1.7.15.  In this incarnation it seems to
>> occur whenever I've run a Cygwin X app from a mintty window.
>> If I've signed on in Windows and never run a Cygwin X app it
>> generally doesn't happen, but I can't be sure it never happens.
>> Every time I've run a Cygwin X app though I can expect to see
>> it after closing (apparently normally) all mintty windows and
>> then log off of Windows.
> 
> Do I understand you correctly that you no longer have any mintty
> windows open when this happens? That's puzzling indeed. Have you
> looked at ye olde Big List Of Dodgy Applications?
> 
> http://cygwin.com/faq/faq.using.html#faq.using.bloda
> 
> Andy

Yes, your understanding is correct.  My bloda spectrum hasn't
changed since 1.7.10 and is pretty well in hand.  When the problem first
appeared in 1.7.10 and I posted about it, a few days later I got a
suggestion to try the latest 1.7.11s snapshot and see if that fixed it.
 It did, I haven't had the problem since until 1.7.15 and 1.7.16s.

This isn't a show stopper, especially since in this incantation it
doesn't happen all the time, however something isn't quite right...
Interesting the Cygwin X apps aggravate the problem.

    Harry

-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Corinna Vinschen]

On May 29 12:41, Harry G McGavran Jr wrote:
> 
> 
> On 05/29/12 12:31, Andy Koppe wrote:
> > On 29 May 2012 17:17, Harry G McGavran Jr wrote:
> >>
> >> Ryan Johnson wrote:
> >>>
> >>> I routinely encounter mintty windows that don't close after
> >>> I exit the login shell they run (even though they contain no
> >>> visible child processes), but they can still be closed using
> >>> the big red "X" in the corner... your problem sounds like
> >>> something more sinister.
> >>>
> >>> Ryan
> >>>
> >>
> >> There is never an "X" to deal with here.  One never know there is
> >> a problem until he does start->Log Off to log out of windows.
> >>
> >> I can normally close any/all mintty windows and then with various
> >> process explorers try to find a mintty process and never find any.
> >> Then when I log out of Windows, Windows claims it has to close
> >> mintty.exe.  This was fixed once in a snapshot of 1.7.10, but
> >> has since returned with 1.7.15.  In this incarnation it seems to
> >> occur whenever I've run a Cygwin X app from a mintty window.
> >> If I've signed on in Windows and never run a Cygwin X app it
> >> generally doesn't happen, but I can't be sure it never happens.
> >> Every time I've run a Cygwin X app though I can expect to see
> >> it after closing (apparently normally) all mintty windows and
> >> then log off of Windows.
> > 
> > Do I understand you correctly that you no longer have any mintty
> > windows open when this happens? That's puzzling indeed. Have you
> > looked at ye olde Big List Of Dodgy Applications?
> > 
> > http://cygwin.com/faq/faq.using.html#faq.using.bloda
> > 
> > Andy
> 
> Yes, your understanding is correct.  My bloda spectrum hasn't
> changed since 1.7.10 and is pretty well in hand.  When the problem first
> appeared in 1.7.10 and I posted about it, a few days later I got a
> suggestion to try the latest 1.7.11s snapshot and see if that fixed it.
>  It did, I haven't had the problem since until 1.7.15 and 1.7.16s.
> 
> This isn't a show stopper, especially since in this incantation it
> doesn't happen all the time, however something isn't quite right...
> Interesting the Cygwin X apps aggravate the problem.

Can you try to find out which snapshot introduced the problem?


Thanks,
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

Re: Mintty Log Off problem (now 1.7.16s)

[Ryan Johnson]

On 30/05/2012 11:52 AM, Corinna Vinschen wrote:
> On May 29 12:41, Harry G McGavran Jr wrote:
>>
>> On 05/29/12 12:31, Andy Koppe wrote:
>>> On 29 May 2012 17:17, Harry G McGavran Jr wrote:
>>>> Ryan Johnson wrote:
>>>>> I routinely encounter mintty windows that don't close after
>>>>> I exit the login shell they run (even though they contain no
>>>>> visible child processes), but they can still be closed using
>>>>> the big red "X" in the corner... your problem sounds like
>>>>> something more sinister.
>>>>>
>>>>> Ryan
>>>>>
>>>> There is never an "X" to deal with here.  One never know there is
>>>> a problem until he does start->Log Off to log out of windows.
>>>>
>>>> I can normally close any/all mintty windows and then with various
>>>> process explorers try to find a mintty process and never find any.
>>>> Then when I log out of Windows, Windows claims it has to close
>>>> mintty.exe.  This was fixed once in a snapshot of 1.7.10, but
>>>> has since returned with 1.7.15.  In this incarnation it seems to
>>>> occur whenever I've run a Cygwin X app from a mintty window.
>>>> If I've signed on in Windows and never run a Cygwin X app it
>>>> generally doesn't happen, but I can't be sure it never happens.
>>>> Every time I've run a Cygwin X app though I can expect to see
>>>> it after closing (apparently normally) all mintty windows and
>>>> then log off of Windows.
>>> Do I understand you correctly that you no longer have any mintty
>>> windows open when this happens? That's puzzling indeed. Have you
>>> looked at ye olde Big List Of Dodgy Applications?
>>>
>>> http://cygwin.com/faq/faq.using.html#faq.using.bloda
>>>
>>> Andy
>> Yes, your understanding is correct.  My bloda spectrum hasn't
>> changed since 1.7.10 and is pretty well in hand.  When the problem first
>> appeared in 1.7.10 and I posted about it, a few days later I got a
>> suggestion to try the latest 1.7.11s snapshot and see if that fixed it.
>>   It did, I haven't had the problem since until 1.7.15 and 1.7.16s.
>>
>> This isn't a show stopper, especially since in this incantation it
>> doesn't happen all the time, however something isn't quite right...
>> Interesting the Cygwin X apps aggravate the problem.
> Can you try to find out which snapshot introduced the problem?
Perhaps figuring out which snapshot between 1.7.10 and 1.7.11 fixed it 
would be faster? It sounds like he didn't go very long between 10 and 
[some] 11s. Not sure it would be as enlightening, though, especially if 
it's one of these cases where some undefined behavior just happens to do 
less-horrible things than usual for some reason...

Ryan


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Corinna Vinschen]

On May 30 11:58, Ryan Johnson wrote:
> On 30/05/2012 11:52 AM, Corinna Vinschen wrote:
> >On May 29 12:41, Harry G McGavran Jr wrote:
> >>
> >>On 05/29/12 12:31, Andy Koppe wrote:
> >>>On 29 May 2012 17:17, Harry G McGavran Jr wrote:
> >>>>Ryan Johnson wrote:
> >>>>>I routinely encounter mintty windows that don't close after
> >>>>>I exit the login shell they run (even though they contain no
> >>>>>visible child processes), but they can still be closed using
> >>>>>the big red "X" in the corner... your problem sounds like
> >>>>>something more sinister.
> >>>>>
> >>>>>Ryan
> >>>>>
> >>>>There is never an "X" to deal with here.  One never know there is
> >>>>a problem until he does start->Log Off to log out of windows.
> >>>>
> >>>>I can normally close any/all mintty windows and then with various
> >>>>process explorers try to find a mintty process and never find any.
> >>>>Then when I log out of Windows, Windows claims it has to close
> >>>>mintty.exe.  This was fixed once in a snapshot of 1.7.10, but
> >>>>has since returned with 1.7.15.  In this incarnation it seems to
> >>>>occur whenever I've run a Cygwin X app from a mintty window.
> >>>>If I've signed on in Windows and never run a Cygwin X app it
> >>>>generally doesn't happen, but I can't be sure it never happens.
> >>>>Every time I've run a Cygwin X app though I can expect to see
> >>>>it after closing (apparently normally) all mintty windows and
> >>>>then log off of Windows.
> >>>Do I understand you correctly that you no longer have any mintty
> >>>windows open when this happens? That's puzzling indeed. Have you
> >>>looked at ye olde Big List Of Dodgy Applications?
> >>>
> >>>http://cygwin.com/faq/faq.using.html#faq.using.bloda
> >>>
> >>>Andy
> >>Yes, your understanding is correct.  My bloda spectrum hasn't
> >>changed since 1.7.10 and is pretty well in hand.  When the problem first
> >>appeared in 1.7.10 and I posted about it, a few days later I got a
> >>suggestion to try the latest 1.7.11s snapshot and see if that fixed it.
> >>  It did, I haven't had the problem since until 1.7.15 and 1.7.16s.
> >>
> >>This isn't a show stopper, especially since in this incantation it
> >>doesn't happen all the time, however something isn't quite right...
> >>Interesting the Cygwin X apps aggravate the problem.
> >Can you try to find out which snapshot introduced the problem?
> Perhaps figuring out which snapshot between 1.7.10 and 1.7.11 fixed
> it would be faster? It sounds like he didn't go very long between 10
> and [some] 11s. Not sure it would be as enlightening, though,

If the code in question has changed a lot, it's only marginally helpful
to refer to a change in older code.  OTOH, knowing both, which snapshot
"fixed" it and which snapshot broke it again could be valuable.


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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

On 05/30/12 12:37, Andy Koppe wrote:
> On 29 May 2012 19:41, Harry G McGavran Jr wrote:
>>
>>
>> On 05/29/12 12:31, Andy Koppe wrote:
>>> On 29 May 2012 17:17, Harry G McGavran Jr wrote:
>>> Do I understand you correctly that you no longer have any mintty
>>> windows open when this happens? That's puzzling indeed. Have you
>>> looked at ye olde Big List Of Dodgy Applications?
>>>
>>> http://cygwin.com/faq/faq.using.html#faq.using.bloda
>>>
>>> Andy
>>
>> Yes, your understanding is correct.  My bloda spectrum hasn't
>> changed since 1.7.10 and is pretty well in hand.
> 
> That doesn't exclude a BLODA problem. It's entirely possible that a
> dodgy app gets away with whatever it's doing with one Cygwin version,
> but fails with the next.
> 
>>>> I can normally close any/all mintty windows and then with various
>>>> process explorers try to find a mintty process and never find any.
>>>> Then when I log out of Windows, Windows claims it has to close
>>>> mintty.exe.
> 
> Are you invoking mintty as administrator and looking at the process
> lists without administrator rights? Otherwise this just defies
> explanation, short of something messing with the Windows kernel, which
> Cygwin (being a user-space DLL) doesn't do.
> 
> Andy

This is with Windows XP SP3.  I am in the administrator group, but I
don't invoke mintty as administrator, only as I normally run as me,
but I am in the administrator group.

It's not impossible that is bloda, but it is odd that it comes and goes
with various cygwin releases then.  It clearly started when I upgraded
to 1.7.10, and clearly disappeared with the 1.7.11s snapshot and then
clearly appeared again with 1.7.15.

    Harry


-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

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...

   Harry



On 05/29/12 10:17, Harry G McGavran Jr wrote:
> 
> Ryan Johnson wrote:
>>
>> I routinely encounter mintty windows that don't close after
>> I exit the login shell they run (even though they contain no
>> visible child processes), but they can still be closed using
>> the big red "X" in the corner... your problem sounds like
>> something more sinister.
>>
>> Ryan
>>
> 
> There is never an "X" to deal with here.  One never know there is
> a problem until he does start->Log Off to log out of windows.
> 
> I can normally close any/all mintty windows and then with various
> process explorers try to find a mintty process and never find any.
> Then when I log out of Windows, Windows claims it has to close
> mintty.exe.  This was fixed once in a snapshot of 1.7.10, but
> has since returned with 1.7.15.  In this incarnation it seems to
> occur whenever I've run a Cygwin X app from a mintty window.
> If I've signed on in Windows and never run a Cygwin X app it
> generally doesn't happen, but I can't be sure it never happens.
> Every time I've run a Cygwin X app though I can expect to see
> it after closing (apparently normally) all mintty windows and
> then log off of Windows.
> 
>     Harry
> 
> 
> 

-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Corinna Vinschen]

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

--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

Corinna wrote:


>If the code in question has changed a lot, it's only marginally helpful
>to refer to a change in older code.  OTOH, knowing both, which snapshot
>"fixed" it and which snapshot broke it again could be valuable.
>
>
>Corinna

This problem first appeared in 1.7.10.  The snapshot I downloaded
that fixed it was "cygwin-inst-20120415.tar.bz2" that I downloaded
on April 17, 2012.  The first go around of posts on this went
without replies for quite some time after 1.7.10 came out.
After one of my posts that questioned whether there were
very many seeing this problem, someone posted that I should
try the latest snapshot, so there is a chance the problem
was fixed in a snapshot previously to the one I downloaded.
The one I downloaded was current as of the day the post appeared
suggesting a snapshot, so it could have been where the fix was.
Nonetheless I responded to that post with a post saying that
that snapshot fixed the problem.  There were no further
posts on the subject until now.

   Harry

-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Corinna Vinschen]

On May 30 11:37, Harry G McGavran Jr wrote:
> Corinna wrote:
> 
> 
> >If the code in question has changed a lot, it's only marginally helpful
> >to refer to a change in older code.  OTOH, knowing both, which snapshot
> >"fixed" it and which snapshot broke it again could be valuable.
> >
> >
> >Corinna
> 
> This problem first appeared in 1.7.10.  The snapshot I downloaded
> that fixed it was "cygwin-inst-20120415.tar.bz2" that I downloaded
> on April 17, 2012.  The first go around of posts on this went
> without replies for quite some time after 1.7.10 came out.
> After one of my posts that questioned whether there were
> very many seeing this problem, someone posted that I should
> try the latest snapshot, so there is a chance the problem
> was fixed in a snapshot previously to the one I downloaded.
> The one I downloaded was current as of the day the post appeared
> suggesting a snapshot, so it could have been where the fix was.
> Nonetheless I responded to that post with a post saying that
> that snapshot fixed the problem.  There were no further
> posts on the subject until now.

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

-- 
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

>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.

    Harry













-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Corinna Vinschen]

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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

>Corinna wrote:
>
>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
>

I thought you had requested in which 1.7.10s snapshot it broke.
So the earliest snapshot I could find for 1.7.10s does have the problem.
It works in 1.7.9.

As I mentioned earlier in cygwin-inst-20120415.tar.bz2, a 1.7.11s
snapshot it's fixed. That's the snapshot that was current when
it was suggested I try the latest snapshot.

So, you must be wanting me to check the 1.7.11s snapshots to see
if it's fixed in an earlier 1.7.11s snapshot.

I'll have to check that out next week when I should have more time.

   Harry

-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

>I thought you had requested in which 1.7.10s snapshot it broke.
>So the earliest snapshot I could find for 1.7.10s does have the problem.
>It works in 1.7.9.
>
>As I mentioned earlier in cygwin-inst-20120415.tar.bz2, a 1.7.11s

That should be cygwin-inst-20120220.tar.bz2.

>snapshot it's fixed. That's the snapshot that was current when
>it was suggested I try the latest snapshot.
>
>So, you must be wanting me to check the 1.7.11s snapshots to see
>if it's fixed in an earlier 1.7.11s snapshot.
>
>I'll have to check that out next week when I should have more time.
>
>   Harry
>
-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Harry G McGavran Jr]

>>I thought you had requested in which 1.7.10s snapshot it broke.
>>So the earliest snapshot I could find for 1.7.10s does have the problem.
>>It works in 1.7.9.
>>
>>As I mentioned earlier in cygwin-inst-20120415.tar.bz2, a 1.7.11s
>
>That should be cygwin-inst-20120220.tar.bz2.
>
>>snapshot it's fixed. That's the snapshot that was current when
>>it was suggested I try the latest snapshot.
>>
>>So, you must be wanting me to check the 1.7.11s snapshots to see
>>if it's fixed in an earlier 1.7.11s snapshot.
>>
>>I'll have to check that out next week when I should have more time.
>>
>>   Harry
>>

I had a little bit of time this afternoon to start on the snapshots
prior to 20120220.  I had enough time to try several of these instead
of the first 1.7.10s snapshot I reported on.  Since it is necessary
to stop any and all cygwin processes before switching the cygwin1.dll's
each time I try a snapsnot, I ended up going through several iterations
where I remembered to stop everything started by cygrunsrv at startup,
but forgot on occasion to stop gpg-agent.  Interestingly, the problem
occurs when I have not stopped gpg-agent.  It turns out that I built
gpg2 on cygwin with the resulting gpg-agent at the same time I had
upgraded to 1.7.15.  So this problem with 1.7.15 and later is because
exiting mintty does not stop the gpg-agent that is somehow associated
with it and according to an earlier post in this thread, unless
a process associated with mintty is started with setsid, if it
is still running you could have a problem like this.

I haven't looked to see how the gpg-agent really gets started when
I fire up mintty, but with gpg2 configured to use gpg-agent, it does.
So, if I stop gpg-agent in ~/.logout under tcsh in mintty, the problem
with 1.7.15 and later disappears.

This is NOT the problem I first reported some months back.  That got
fixed with cygwin-inst-20120220.tar.bz2.  I was not using gpg-agent or
gpg2 prior to 1.7.15 and just happened to do the 1.7.15 upgrade the same
day I installed gpg2 and when I logged off windows got the problem
with Windows wanting to end mintty even when it had been properly
terminated ever since.

So thanks for everyone's patience in what turned out to be a red-herring.



-- 

Harry G. McGavran, Jr.

E-mail: w5pny@w5pny.com


--
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

Re: Mintty Log Off problem (now 1.7.16s)

[Christopher Faylor]

On Sat, Jun 02, 2012 at 03:17:34PM -0600, Harry G McGavran Jr wrote:
>>>I thought you had requested in which 1.7.10s snapshot it broke.
>>>So the earliest snapshot I could find for 1.7.10s does have the problem.
>>>It works in 1.7.9.
>>>
>>>As I mentioned earlier in cygwin-inst-20120415.tar.bz2, a 1.7.11s
>>
>>That should be cygwin-inst-20120220.tar.bz2.
>>
>>>snapshot it's fixed. That's the snapshot that was current when
>>>it was suggested I try the latest snapshot.
>>>
>>>So, you must be wanting me to check the 1.7.11s snapshots to see
>>>if it's fixed in an earlier 1.7.11s snapshot.
>>>
>>>I'll have to check that out next week when I should have more time.
>>>
>>>   Harry
>>>
>
>I had a little bit of time this afternoon to start on the snapshots
>prior to 20120220.  I had enough time to try several of these instead
>of the first 1.7.10s snapshot I reported on.  Since it is necessary
>to stop any and all cygwin processes before switching the cygwin1.dll's
>each time I try a snapsnot, I ended up going through several iterations
>where I remembered to stop everything started by cygrunsrv at startup,
>but forgot on occasion to stop gpg-agent.  Interestingly, the problem
>occurs when I have not stopped gpg-agent.  It turns out that I built
>gpg2 on cygwin with the resulting gpg-agent at the same time I had
>upgraded to 1.7.15.  So this problem with 1.7.15 and later is because
>exiting mintty does not stop the gpg-agent that is somehow associated
>with it and according to an earlier post in this thread, unless
>a process associated with mintty is started with setsid, if it
>is still running you could have a problem like this.

That is because a subprocess which still has an an open pty associated
with it maintains a connection to the originator of the pty.  setsid
breaks that connection.

cgf

--
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