-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[NBug] SSH key file could not be found #10650
Comments
Fixed in 4.0.2. Please update.
|
Can it be that with the new version (not sure if it's 4.0.2 or 4.x in general), Git Extension always tries to start the Pagent, even though it's already running and I don't have "Automatically start authentication client when a private key is configured for a remote" checked (nor do I have a private key configured)? It's not really breaking anything, but it's a bit annoying to get a "Pageant is already running" dialog I need to click away on every push operation... |
In which version are you seeing this behaviour?
|
4.0.2.16100 |
I also tested this on my other machine and can confirm:
I am using Putty and already have a pageant running when I start / use GitExtensions. There are no keys configured in GitExtensions and the option "Automatically start authentication client..." in the SSH settings is disabled. Should I open a separate issue for this or can we leave it here? Thanks for your efforts! 🙏 |
I experienced this same issue, I had to go into |
I habe Putty selected, my Paths are correct, but GitExtensions still wants to start a new agent even though the external one is already running. @doctorfox , are you using an external pageant? |
This could be the side effect from this #10545 (comment). gitextensions/GitUI/Infrastructure/PuttyHelpers.cs Lines 74 to 79 in 4cb3e5d
Could you please provide a stable repro? /cc: @gerhardol @vbjay |
Yes, that seems very likely. I guess the problem is the way it is determined whether pageant is running:
This will only work if pageant is the executable defined in GitExtensions. However, in my case, the pageant service is provided by the KeePass plugin KeeAgent, so GitExtensions will think it's not running. When I just remove the path in GitExtensions config, I will also get an error "SSH agent could not be found. '' is Putty installed?". The root cause for me is that GitExtensions wants to start pageant even though I absolutely don't want it to. The code should take into consideration the value of the flag "Automatically start authentication client when a private key is configured for a remote" in the SSH settings. If this is not checked, GitExtensions should not try to start pageant and doesn't need to check if it's running either... |
History:
No one in the core team is using PuTTY, vbjay is the only regular contributor I know using PuTTY. I suggest a new issue is found to handle possible tweaking of PuTTY behavior. |
Yes. |
Thanks for the input, I've created a separate issue for this: #10656 |
Closing as the "key not found" issue is fixed in 4,0,2. The "external pageant handling" is tracked under #10656. |
Environment
Issue description
''
After rebase, trying to force push with lease like what I used to do in previous version.
Steps to reproduce
Trying to push a local branch to origin but this error pops up.
Did this work in previous version of GitExtensions?
Yes
Diagnostics
No response
The text was updated successfully, but these errors were encountered: