public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygwin-3.1.0 and mintty from desktop shortcut
Date: Thu, 12 Mar 2020 20:39:39 +0100	[thread overview]
Message-ID: <87d09htlac.fsf@Rainer.invalid> (raw)
In-Reply-To: <c3c4e96a-63bc-5b7d-5fb5-2ad21ec36cdf@emrich-ebersheim.de> (Rainer Emrich's message of "Thu, 12 Mar 2020 03:56:01 +0100")

Rainer Emrich writes:
> I really don't know if this the same issue. But I had similiar symptom
> after upgrade from 3.0.7 to 3.1.4 on Windows 7. The mintty window pops
> up, but I got no command prompt. The bash shell used all of one CPU for
> ever. I tried several things. The solution after hours was uninstalling
> the gettext package. That's reproducable. After installing the gettext
> package I get the hang. After uninstalling all's back to normal. That's
> strange.

I don't really want to imagine how you came up with that observation,
but yes, that's the same problem I am facing.  This is my current
workaround now:

1. Rename /usr/share/locale to something else, like local.bak.
2. Start mintty in the usual way.
3. Rename the directory from step 1 back to /usr/share/local.
4. Work just like the problem never existed either in the shell running
inside the mintty or even start a new mintty.


Andrew, can we have a Goldstar for Rainer, please?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

  reply	other threads:[~2020-03-12 19:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 23:26 [ANNOUNCEMENT] cygwin 3.1.0-1 Corinna Vinschen
2019-12-17  6:35 ` Thomas Wolff
2019-12-17  8:49   ` [GOLDSTAR][PLUSH HIPPO] " Corinna Vinschen
2019-12-17 20:58     ` Andrew Schulman via cygwin
2019-12-17 18:57 ` cygwin-3.1.0 and mintty from desktop shortcut (was: [ANNOUNCEMENT] cygwin 3.1.0-1) Achim Gratz
2019-12-18  9:07   ` Corinna Vinschen
2019-12-18 16:56     ` cygwin-3.1.0 and mintty from desktop shortcut Achim Gratz
2020-03-11 17:47       ` Achim Gratz
2020-03-11 19:51         ` Corinna Vinschen
2020-03-12  2:56           ` Rainer Emrich
2020-03-12 19:39             ` Achim Gratz [this message]
2020-03-12 21:36               ` Thomas Wolff
2020-03-13  1:03               ` Takashi Yano
2020-03-13  2:01                 ` Takashi Yano
2020-03-13 15:09                   ` Rainer Emrich
2020-03-13 21:26                   ` Achim Gratz
2020-03-13 22:20                     ` Ken Brown
2020-03-14 16:11                       ` Achim Gratz
2020-06-06 11:20                 ` ASSI
2020-06-07  1:35                   ` Takashi Yano
2020-06-07  5:29                     ` ASSI
2020-06-07  6:15                     ` Brian Inglis
2020-06-07  7:42                       ` Takashi Yano
2020-06-07  9:23                         ` Takashi Yano
2020-06-08  3:20                           ` Brian Inglis
2020-06-08 10:27                             ` Takashi Yano
2020-06-08 19:24                               ` Brian Inglis
2021-03-22 20:13                   ` Achim Gratz
2020-03-12 10:57           ` Takashi Yano
2020-03-12 19:46             ` Achim Gratz
2019-12-18 12:28   ` cygwin-3.1.0 and mintty from desktop shortcut (was: [ANNOUNCEMENT] cygwin 3.1.0-1) Takashi Yano
2019-12-18 17:17     ` cygwin-3.1.0 and mintty from desktop shortcut Achim Gratz
2019-12-18 10:18 ` [ANNOUNCEMENT] cygwin 3.1.0-1 Henning
2019-12-18 11:25   ` Corinna Vinschen
2019-12-20  9:40     ` Henning
2019-12-20 10:22       ` Corinna Vinschen
2019-12-20 16:20         ` Henning
2020-01-13 21:30   ` Houder
2020-01-14  0:20     ` Ken Brown

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=87d09htlac.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).