After cygwin 3.2 update windows terminal input is sometimes broken

Tomas Tumelionis
Tue Jun 8 12:41:52 GMT 2021

Sorry for the vague description. After recreating all my current
configuration from scratch I've found that it is only with  oh my zsh
default theme - robbyrussell - I am facing the issue. Well atleast with my
version of zsh+cygwin+windows terminal. Changing the theme made everything
work again and splitting windows terminal pane did not make input stuck. To
be exact, window resize is the root problem. This kinda points towards the
windows terminal issue, but with previous versions of stack
(cygwin+zsh+ohhmyzsh) it did work ok. Leaving appropriate github issues,
maybe someone will be able to provide more insights:
ohhmyzsh -
windows terminal -

My stack:
Terminal: windows terminal preview <>
Cygwin: CYGWIN_NT-10.0 LAT-5F3FMQ2 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64
Shell: zsh 5.8 + oh my zsh (706b2f3) + theme robbyrussell (default)
Windows version: 10.0.19043 N/A Build 19043

On Tue, 8 Jun 2021 at 14:42, L A Walsh <> wrote:

> On 2021/06/06 22:08, Tomas Tumelionis via Cygwin wrote:
> > Been using windows terminal preview (this is still actual with current
> > latest version 1.9) and after cygwin 3.2 update windows terminal input is
> > broken after:
> > * splitting pane
> > * moving terminal window to other window
> > * sleeping pc
> > This means that if I open the terminal and split pane, I can not enter
> text
> > into the previous pane forever.
> >
> ----
>     Does the cygwin terminal still work?  Seems like you are reporting
> a Windows problem in cygwin.  What does cygwin have to do with
> a windows terminal -- it doesn't use cygwin at all, does it?  So
> how does an update in cygwin cause a windows problem?
>     You realize MS update your Terminal preview's OS almost daily, most
> the time without you realizing it.  It's more likely they broke
> it at the same time cygwin had an update, than something in cygwin
> affecting Win10...
>     If they have a version of the Terminal preview that runs on
> Win7, though, I'll be happy to have a look at the problem... ;-)

More information about the Cygwin mailing list