public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Mintty does not close after "exit" command
@ 2017-05-24  9:27 Dani Moncayo
  2017-05-24 11:32 ` Andrey Repin
  2017-05-25  9:57 ` Sky Diver
  0 siblings, 2 replies; 4+ messages in thread
From: Dani Moncayo @ 2017-05-24  9:27 UTC (permalink / raw)
  To: cygwin

Hi,

subject line says it all.

I've been experiencing this problem for some months, on windows 10.
But the problem does not appear in another windows 8.1 system I use.

To reproduce the problem, just open the standard cygwin terminal (e.g.
by double-clicking the desktop icon), an then type the "exit" command
in the bash shell.

I see a "logout" message for a fraction of a second, then the terminal
becomes empty (without text), but the mintty window remains visible
but unresponsive, with the title bar showing "~ (Not Responding)".


-- 
Dani Moncayo

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Mintty does not close after "exit" command
  2017-05-24  9:27 Mintty does not close after "exit" command Dani Moncayo
@ 2017-05-24 11:32 ` Andrey Repin
  2017-05-24 12:54   ` Dani Moncayo
  2017-05-25  9:57 ` Sky Diver
  1 sibling, 1 reply; 4+ messages in thread
From: Andrey Repin @ 2017-05-24 11:32 UTC (permalink / raw)
  To: Dani Moncayo, cygwin

Greetings, Dani Moncayo!

> Hi,

> subject line says it all.

> I've been experiencing this problem for some months, on windows 10.
> But the problem does not appear in another windows 8.1 system I use.

> To reproduce the problem, just open the standard cygwin terminal (e.g.
> by double-clicking the desktop icon), an then type the "exit" command
> in the bash shell.

> I see a "logout" message for a fraction of a second, then the terminal
> becomes empty (without text), but the mintty window remains visible
> but unresponsive, with the title bar showing "~ (Not Responding)".

Anything suspicious in logout script?
One known cause if it could be reproduced fairly easy with ssh to a remote
host. Once ssh session ends, MinTTY will stick after exit, until you press
Enter.


-- 
With best regards,
Andrey Repin
Wednesday, May 24, 2017 13:04:08

Sorry for my terrible english...


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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Mintty does not close after "exit" command
  2017-05-24 11:32 ` Andrey Repin
@ 2017-05-24 12:54   ` Dani Moncayo
  0 siblings, 0 replies; 4+ messages in thread
From: Dani Moncayo @ 2017-05-24 12:54 UTC (permalink / raw)
  To: cygwin

> Anything suspicious in logout script?

I don't think so.  Until now, I didn't even know about such a script
(I guess it's "/etc/bash.bash_logout").

Thanks anyway.

-- 
Dani Moncayo

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Mintty does not close after "exit" command
  2017-05-24  9:27 Mintty does not close after "exit" command Dani Moncayo
  2017-05-24 11:32 ` Andrey Repin
@ 2017-05-25  9:57 ` Sky Diver
  1 sibling, 0 replies; 4+ messages in thread
From: Sky Diver @ 2017-05-25  9:57 UTC (permalink / raw)
  To: cygwin

On Wed, May 24, 2017 at 11:42 AM, Dani Moncayo wrote:
> To reproduce the problem, just open the standard cygwin terminal (e.g.
> by double-clicking the desktop icon), an then type the "exit" command
> in the bash shell.
>
> I see a "logout" message for a fraction of a second, then the terminal
> becomes empty (without text), but the mintty window remains visible
> but unresponsive, with the title bar showing "~ (Not Responding)".

I've seen this happen several times in the past few days.
This may be related to the fact that I'm installing cygwin a lot these days.
It may happen after installing a package that doesn't require to close
any open cygwin terminal.
Usually I close everything by default but since I'm installing a lot
lately I sometimes skip it if it's not required (e.g. installing a php
extension).

Maybe you have some cygwin service running in the background (you can
check it with: cygrunsrv -L).
Regardless, maybe a full rebase could help.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-05-25  7:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-24  9:27 Mintty does not close after "exit" command Dani Moncayo
2017-05-24 11:32 ` Andrey Repin
2017-05-24 12:54   ` Dani Moncayo
2017-05-25  9:57 ` Sky Diver

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