ctrl+c in gitbash on windows terminal kills ssh remote sessions

[avasant21]

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19043.0

Other Software

Gitbash - mintty 3.5.2

Steps to reproduce

1. Added the gitbash as default profile in Windows Terminal
2. Logged into ssh remote systems
3. Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash

This behavior is not observed when directly running on Gitbash terminal

Expected Behavior

ctlr+c should just interrupt the current process not the sessions

Actual Behavior

Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash

[fredrik-corneliusson]

Bug is also discussed in git for windows:
git-for-windows/git#3657 (comment)

[akulbe]

Okay, I thought this issue was with my keyboard. This is happening here multiple times per day, and it's making me crazy. 🤪

[poonsakn]

This also happen to me when using puTTY via plink command.

Windows Terminal
Version: 1.11.3471.0

[zadjii-msft]

huh, so this is like the opposite of #8034

[macdjord]

I've been seeing this every since I updated from git version 2.35.1.windows.2 to git version 2.36.0.rc0.windows.1.

Also, I've noticed something odd: after accidentally killing an SSH session in this way, the terminal stops echoing characters when I type them.

[aschaepper]

Got the same behavior but also with the older Git Version:
git version 2.35.1.windows.2
It only hapens in the git shell, other shells like powershell work.

Also the keyboard buttons home and end seem to behave weird, but only on some kind of target machines (ARM/Yoctolinux/Busybox in my case) on Ubuntu 20 home and end works. but Ctrl-c also closes the connection.

Running windows Terminal 1.12.10733.0 from the store on:
Windows 11:
21H2
OSBuild: 22000.593
Windows Feature Experience Pack 1000.22000.593.0

Reinstalled Windows Terminal, Reset the settings nothing worked so far.

[WereCatf]

I noticed this bug a while ago already and haven't found a fix for it. So far I've stuck to 2.34.1, because I really need SSH and ctrl+c to work.

Would be nice to know, if the issue is caused by Windows Terminal or Gitbash, though.

[kennyhyun]

ssh in Command Prompt (on Windows Terminal) has no such issue

[joaommartins]

Seems to be fixed in git version 2.36.0.windows.1, running on Windows Terminal build 1.12.10982.0.

[zadjii-msft]

@joaommartins that's great to hear! I had a sneaking suspicion this was a git bash issue, but I was having a hard time tracking this down.

Can any other folks confirm/? Hopefully we can just close this one out ☺️

[WereCatf]

I can confirm, works fine with 2.36.0 again.