Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search Sign up Reseting focus

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to interrupt vagrant with CtrlC from a cygwin terminal #9387

rossengeorgiev opened this issue Jan 19, 2018 · 14 comments

Unable to interrupt vagrant with CtrlC from a cygwin terminal #9387

rossengeorgiev opened this issue Jan 19, 2018 · 14 comments

Comments

rossengeorgiev commented Jan 19, 2018 •

Vagrant version

$ vagrant -v Vagrant 2.0.0

Host operating system

Windows 10 + Cygwin

Expected behavior

Press Ctrl+C and vagrant process gets interrupted

Actual behavior

I get my prompt back, but the vagrant process continues to run and output to the terminal.
Essentially, I'm unable to cancel any command.

Steps to reproduce

  1. vagrant up inside cygwin terminal (mintty)
  2. Press Ctrl+C

The text was updated successfully, but these errors were encountered:

chrisroberts added core host/windows labels Jan 25, 2018 bizxta commented Aug 5, 2019

Same issue here on Windows 7 and vagrant 2.2.4.

jbonhag added this to the 2.2 milestone Apr 24, 2020 chrisroberts modified the milestones: 2.2, 2.2.9 May 4, 2020 briancain commented May 4, 2020

Thanks for reporting this bug. I'm sure this was a real issue when originally reported (our fault for not looking sooner!) but there have been multiple Vagrant releases since the original report. I just tried to reproduce this with the latest Vagrant and Cygwin on windows 10 and I was able to interrupt Vagrant without issue. I'm going to close this issue now and request you reopen the issue if you're still experiencing this problem. I'm sorry this wasn't looked at earlier