-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
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
tmux would stuck ssh-agent (auto-login) #1122
Comments
I do not think this is anything to do with tmux. |
Hmm... it is strange. Only severals quit & enter |
Are you sure you are not ending up with 2 ssh-agent or something?
…On 18 Oct 2017 12:58 pm, "eromoe" ***@***.***> wrote:
Hmm... it is strange. Only severals quit & enter tmux would happen , so
you mean it is by ssh-agent?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1122 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AASkc6oIFCOVvWYT6SsFu5zoG9J2502Sks5stefvgaJpZM4P9lHz>
.
|
What do you mean I come up one thing, msys has its ssh-agent, which is different from git-bash's . And the version is different too.It doesn't happen on my work PC today, may due to I update all pakcages today . My home PC is using old ssh package. I would tried that. |
OK let me know if that fixes it. |
Never happen again until now, after update ssh and .tmux.conf PS: I also found there were some sh.exe(6 ~11) runing on background after enter tmux yesterday later . Also may by the .tmux.conf I used. What ever, it is solved now. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Several times enter & quit tmux may cause this problem. tmux would make ssh-agent freezed(stuck or broken) . I have to kill all ssh-agent and restart tmux. Then works some time, error again.
You can see this,
gif shows:
After ssh-agent killed, tmux could work with ssh-agent again, would not stuck. But severals quit & enter would happen again.
logs:
tmux-server-13592.log
tmux-client-17148.log
ssh-agent is auto-start, script by https://help.github.com/articles/working-with-ssh-key-passphrases/#auto-launching-ssh-agent-on-git-for-windows .
Doesn't see this problem when only using git-bash, msys2(not enter tmux).
In addition, ssh-agent seems would expire the passphrases after a long time, then when I start a new console(git-bash/msys2), would prompt to ask me enter passphrases. Maybe that is not by expire mechanism, because github's auto-start script not show code about this. I don't know if it is relative, just let you know.
The text was updated successfully, but these errors were encountered: