From: Sky Diver <skydivergm@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Mintty does not close after "exit" command
Date: Thu, 25 May 2017 09:57:00 -0000 [thread overview]
Message-ID: <CADWQZEtfhynLghBok1Gm6JzFDBgkPbLxRxH4H4EAtSOcwG+1qw@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0iiRvbGcd1_BYTXT+jRmUs_oYMLezVqT5Q6iFN-1QeL4g@mail.gmail.com>
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
prev parent reply other threads:[~2017-05-25 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 9:27 Dani Moncayo
2017-05-24 11:32 ` Andrey Repin
2017-05-24 12:54 ` Dani Moncayo
2017-05-25 9:57 ` Sky Diver [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADWQZEtfhynLghBok1Gm6JzFDBgkPbLxRxH4H4EAtSOcwG+1qw@mail.gmail.com \
--to=skydivergm@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).