From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: mintty hangs when started from desktop shortcut (was: [ANNOUNCEMENT] cygwin 3.1.4-1)
Date: Wed, 19 Feb 2020 20:30:00 -0000 [thread overview]
Message-ID: <87mu9e5nh8.fsf@Rainer.invalid> (raw)
In-Reply-To: <announce.20200219115927.387179-1-corinna-cygwin@cygwin.com> (Corinna Vinschen's message of "Wed, 19 Feb 2020 11:59:27 +0100")
Corinna Vinschen writes:
> The following packages have been uploaded to the Cygwin distribution:
>
> * cygwin-3.1.4-1
> * cygwin-devel-3.1.4-1
> * cygwin-doc-3.1.4-1
Unfortunately the problem that I reported already for the 3.1.0 release
persists. When starting mintty from a desktop shortcut as I usually do,
it hangs while consuming one CPU.
My previous workaround no longer works interestingly enough, so starting
mintty from a Cygwin shell started in cmd via cygwin.bat now _also_
hangs in the same way. As before, starting any non-Cygwin program like
cmd or strace with the mintty shortcut works correctly and mintty
doesn't hang.
The new workaround is to start a mintty with cmd inside, then from this
cmd run the command that I'd usually invoke via the desktop shortcut
(i.e another mintty with my login shell). That works and I can then
work in that mintty without any problems (and close the first one).
This _only_ happens on my work laptop (Windows Enterprise 1803).
It doesn't happen on a system with Windows Server 2016 (that's 1607 I
think) nor does it happen on Windows Pro 1909 or Windows Home 8.1.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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:[~2020-02-19 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 11:04 [ANNOUNCEMENT] cygwin 3.1.4-1 Corinna Vinschen
2020-02-19 17:02 ` howto rollback cygwin 3.1.4-1 to older 3.0.7 version? Eugene Klimov
2020-02-19 18:11 ` Marco Atzeri
2020-02-19 18:43 ` Marco Atzeri
2020-02-20 4:01 ` Eugene Klimov
2020-02-20 9:13 ` Thomas Wolff
2020-02-20 9:52 ` Eugene Klimov
2020-02-20 10:31 ` Takashi Yano
2020-02-20 12:02 ` Eugene Klimov
2020-02-20 3:55 ` Eugene Klimov
2020-02-19 23:52 ` Takashi Yano
2020-02-20 4:51 ` Eugene Klimov
2020-02-20 10:25 ` Takashi Yano
2020-02-20 12:05 ` Eugene Klimov
2020-02-24 8:02 ` Houder
2020-02-19 20:30 ` Achim Gratz [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=87mu9e5nh8.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).