First I want to say, pls believe me this is not a problem about command less a file or a problem could solve by typing q(or:q whatever)...
My trouble is that the Powershell get stuack only with a flashing underline after a git command finished. Here the 'finish' define as a command should have been exited. An example picture is as fllow.
As you can see, the command git log -2 should be exited immediately. There's absolutely no need for me to enter q or :q. There is same trouble when I pressed a key q after run command git log or git diff.
However, after I run the powershell as Administratior user, the trouble disappears. The picture is as fllow.
I have tried many ways, but the problem always be there. The ways I have tried include downgrading the git version, rm the git repo dir and re-clone.
I guess it may be the problem about file permissions, but I have no idea to solve it, please help me(ó﹏ò｡)
When I'm using git and running any command which intends to open an editor (like git commit or git rebase -i) it opens up vim as expected in powershell but it behaves very strangely.
If i press <Ctrl + Right arrow> it erases a lot of content in the file and turns insert mode on but it should advance the cursor to the end of the next word keeping the current mode
If i open COMMIT_EDITMSG in another terminal with powershell and proceed with E (Forcing it not to use swap) it works just fine. I tried different terminal emulators like cmd and powershell terminal but it works the same (weird) way in all of them
Fixed it using neovim instead of vim
Note that it also act strangely when leaving vim, displaying the commit message poorly:
This is followed by microsoft/terminal issue 9359, and mentioned in the latest Git For Windows release 2.34: check if Git 2.34 would behave better with vim in your case.
I'm using cypress for test automation and when running a test spec from the Git for Windows bash terminal I get weird characters in the results output:
cypress spec run in Git for Windows bash -
If I run cypress from a Windows command prompt the output characters are correct:
cypress spec run in Windows Command Prompt -
I'm using Windows 7, cypress 5.1.0, and Git for Windows 2.28.0 with mintty 3.2.0
Any thoughts on how to correct this?
The issue is described in this GitHub issue.
The problem is that Cypress is sending UTF-8 encoded text through its stdout which is mangled by Windows before being received by Mintty (which is what hosts bash and runs git on Windows).
I understand that Mintty doesn't yet instruct Windows to not mangle the stdout it processes - (cmd.exe does, however, which is why it works there) - but we can do that ourselves by changing our Windows OEM Code Page setting using the chcp program (located at C:\Windows\System32\chcp.com and yes, that's a .com, not .exe). You can add a command to your .bashrc file so it will always run when you fire up Mintty:
Open mintty on Windows - presumably this starts a bash shell.
Go to your home directory (i.e. cd ~)
Open or create a .bashrc file.
Put this in the file (update the path to your chp.com program as appropriate):
/c/Windows/System32/chcp.com 65001
Then restart the terminal window and it should work.
As both #digijay and #Dai replied above the cause of the issue is described here https://github.com/git-for-windows/git/issues/2806
The issue was resolved with the next release of git-for-windows. Prior to the fix being released, I solved the issue for myself by simply running this at the bash command line before running my cypress run command:
> cmd //c chcp 65001
I have had up to 8 git bash terminals running at the same time before.
Currently I have only 2 up.
I have not seen this error before and I am not understanding what is causing it.
Any help would be appreciated!
Picture attached:
Found a similar issue and solution in google groups
I opened a windows command prompt and ran the command
$ tasklist
It looks as though the ssh connections I had made in my git bash shells weren't being closed when those windows were closed and were hanging the available git bash shell windows.
This may be a dangerous solution but from the windows command prompt I ran
$ taskkill /F /IM ssh.exe
Everything appears to be working again after this. It may not have directly been an issue of orphan processes, but this worked for at least for me.
Additional note: you can also kill other processes, for example like:
$ taskkill /F /IM vim.exe
In my case, it was related with the use of VS code. Previously I have opened VS code using a git bash terminal and executing
code .
then closing the terminal.
The problem is solved by closing all the VS code windows opened.
When you have any editor or IDE configure to open a terminal as git bash, then when the IDE/IDE is running, the git bash will spin up bash from "C:\Windows\System32\bash.exe" and any other attempt to open bash from a separate window is likely to crash.
The best solution is to kill the IDE/Editor bash and open from a new window or continue from the IDE/Editor command.
I see the problem on windows in git bash when I kill my git bash console without using exit. I found killing ssh-agent.exe task from windows task manager to fix the problem.
I address this with a workaround:
Close the Git Bash window.
Open Task manager.
Find the 'Git for Windows' process.
Kill it.
Open Git Bash.
It should be ok now.
Open task manager and kill process with name bash, this worked for me.
This happens when you exit git bash without terminating existing process. Just try and kill those processes that you started from git bash.
I was running node process inside git bash, so I killed all node processes
Steps to kill
Open Task Manager
Goto Details Tab
Look for node.exe(you look for you processes)
Kill it each and every node process
Open Git Bash again
To make life easier (this problems happens quite often) create a file called fixbash.bat in home directory and paste this:
taskkill /F /IM ssh-agent.exe
When problem occurs just open cmd and type fixbash.bat to fix a problem.
Or
Just paste the taskkill command into your cmd if you don't want to create a script.
Restart your machine.
(The other answers did not work for me. (I didn't try reinstalling. Restarting is probably faster.))
finally figured out what was causing this.
if we use code like this (explicitly or implicitly) i.e. in .bashrc file
eval $(ssh-agent -s)
ssh-add ~/.ssh/id_rsa
it spawns a new process.
if you don't exit it and just close the window, that process is still running. so each new bash opened just keeps adding new ones w/out disposing old ones.
when done with a bash window, simply hit ctrl+d or type exit to kill the agent process, and you should not run out of forks.
In my Case I need to kill Git bash in Windows.
So opened Command Prompt and ran below command
$ tasklist
It will list down all running tasks, then need to kill bash.exe task using below command
$ taskkill /F /IM bash.exe
For me (or anyone running protractor, which may spin up a standalone Selenium/WebDriver server), I needed to taskkill the specific webdriver which was running my tests.
So just a different argument:
or your chromedriver version may vary
taskkill /f /im chromedriver_2.34.exe
Note your driver may vary:
IEDriverServer*.*.*.exe vs chromedriver_*.**exe
Your driver may version may vary:chromedriver_2.34.exe vs chromedriver_2.33.exe
This problem got worse after protractor quit without closing the automated /test-driven browser, (due to a separate issue I don't yet understand.) Naturally many chromedriver tasks remain running, that's why kill them.
Seems to be an issue with the processes launched from the git bash indeed, like #mamacdon suggested in his comment on the top answer by #Scott Newson.
For me, the issue appeared if I launched a vscode from the bash with code, and if this instance of vscode launched an integrated git terminal while the original bash was still running.
Doesn't matter whether that terminal was launched at the start or later, as long as it was while the original bash was still running.
Didn't happen when the bash was closed before the integrated terminal was opened. Didn't differentiate between exit and closing bash via windows. Didn't happen with another older bash window still running.
The way to deal with it was for me to close the terminals in vscode with exit or 'Kill Terminal' (be careful not to mix that up with 'close pane'), or of course, closing vscode itself.
If you get this error try to remember what you launched from the bash and kill it. If the other answers worked for you, it's probably just that these are the things launched by your bash or launched by processes you launched from the bash and they somehow were getting a child of your original bash.
If you are using Visual Studio Code and you can't find ssh-agent.exe or can't taskkill it and after opening Git Bash you get that error, just go to your VSCode open Terminal>New Terminal and just press the trashbin icon the (Kill Terminal). e.g (1:bash) if you got multiple then just kill them all and you should be good.
I tried to kill all my git terminals in task manager solves the problem.
This works for me too.
good luck.
Open your Task manager, search "sh" procces and kill them.
Good luck
In my case, I was running jupyter-notebook from Git Bash and closed the terminal without closing the notebook. When I closed all running git bash terminals and tried to open new terminal, this gave me the error:
Error: Could not fork child process: There are no available terminals (-1).
Solution
taskkill /F /IM jupyter-notebook.exe
After that, I was able to run commands in git bash terminal.
i found that killing msys2 terminal in task manager solves the problem
On a more recent version of git for windows, the process to kill in task manager was "GitExtensions.exe". Killed that and the terminals restarted with no issues.
Please find the ssh-agent process in the Task Manager window.
After you stop or kill the ssh-agent process the error will disappear.
Open Task manager, find bash.exe process and kill it. Helped in my case.
In my case I had visual studio code running and closing it resolved the issue.
Windows 10 this worked for me:
1) open cmd as administrator
2) type:
taskkill /f /im git-bash.exe
3) If there was an Error: The process "ssh-agent.exe" not found. then:
type:
tasklist
4) Find and kill every process with words like "bash" or "git" (This may be a dangerous solution, but once you will find the process name, next time you will know.)
taskkill /f /im ***.exe
Im my case, the solution was to close Visual Studio Code -where I had console running too without noticing-
After closing it all back to normal.
Hope this helps someone.
In my case, I needed to kill sh.exe
taskkill /F /IM sh.exe
Many answers here are suggesting different processes they need to kill in order to be able to open a new Git Bash terminal. In my case there were multiple conhost.exe processes running which I had to kill before I could open another window successfully.
Perhaps more importantly, is why it happened. I think I know exactly what I did which led to this state. I noticed that when typing git log, if I then resize my Git Bash window, it would hang. (Pressing q would not exit the log and I could no longer type commands.) I ended up closing the window and opening another one. I was doing some testing of this repeatedly to see if I could figure out a solution to the freezing after resizing, and after doing this multiple times (probably around 10 times), I received the error in this question. The results of my testing are:
Opening a new Git Bash Window starts the following processes:
conhost.exe
git-bash.exe
git.exe
mintty.exe
Now, when you type git log, 4 additional processes open:
bash.exe
conhost.exe
git.exe
less.exe (this will only stay open if your log cannot fit on one screen)
When you close Git Bash, those 8 processes all normally go away. However, due to a bug, (which I think is possibly in less.exe) when you resize the window while viewing the log, Git Bash hangs. If you now close the window only 6 of the 8 processes close. Both less.exe and conhost.exe stay active. In my case, eventually enough conhost.exe processes built up and caused whatever the issue is that leads Git Bash displaying the error and not starting.
That said, I tried to repeat the issue but gave up after 20+ tries, which was more conhost processes than I had to kill when I was in the problem state. I suspect it's not a process number but something about the state of one or more processes that leads to the error. Obviously since other answers mention closing different processes, the "thing" that isn't closing properly and fighting against Git Bash can vary, depending on what tools you're using.
Note, I'm using Git version: 2.37.1.windows.1.
For windows, in task-manager kill sh.exe.
In my case the problem was the file [git_install_dir]/etc/nsswitch.conf
I previously followed the instructions given here:
https://cygwin.com/faq.html#faq.using.startup-slow.
But this caused the "Could not fork" error instead.
My wrong nsswitch.conf file was:
passwd: files
group: files
So I restored the file and problem solved. Now my [git_install_dir]/etc/nsswitch.conf is:
passwd: files db
group: files # db
db_enum: cache builtin
db_home: env windows cygwin desc
db_shell: env windows # cygwin desc
db_gecos: env # cygwin desc
Tried the following solution which worked for me:
Kill all existing git.exe
Added my credentials for BitBucket in the Windows Credential manager under the generic credentials section.
Reinstalled git, it is now working fine.
In system bash type:
ps
Kill any bad looking process:
kill -9 <ID>
Worked for me.