-
Notifications
You must be signed in to change notification settings - Fork 28.7k
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
Bug: Git: ssh_askpass: exec(/usr/X11R6/bin/ssh-askpass): No such file or directory #32097
Comments
Experiencing the same issue. macOS Sierra 10.12.4 and VSCode Insiders installed yesterday. |
I too can confirm this bug. Hosting my own internal git server on a Raspberry PI, which is configured to require a password on push. See this exact same error running OSX El Capitan and the latest version of VS Code, attempting to push from within the app. |
Same error here trying to push from mac OS X 10.12.5 Sierra Works via command line |
Same issue, after updating to mac OSX Sierra. |
Reinstall vscode fixed this. |
In my case, it's caused by updating of mac OS, makes git lose passphrase of my ssh key. After |
@shunia Thank you, though I don't think this can be the final solution, because it would mean that you would have to reinstall VSCode for every new ssh key. In my view, that's not acceptable. VSCode etc. should fix this. |
In my case, I just downloaded and installed vscode and tried to use git pull from the vscode ui. I got the error |
Wow, yes, this indeed seems to work. Which is pretty weird, because I set up everything beforehand to communicate between my computers and my server server through SSH via Terminal and also SourceTree, and that all worked a treat, no weird errors in SourceTree's "console" output. |
Same issue here w/ High Sierra. @shunia solution did not work in this case. Note that this is for a project with a new key added to gitlab. I've not logged this machine into gitlab before. Also, by default, macOS doesn't have Indeed, if I manually clone via terminal,
now, everything works. So it seems that the authenticity check raises an exception to the |
@flipphillips I do think this is a bug or something goes wrong inside vscode, you pointed this out. |
I've used command below to fix it:
Hope it will be helpful workaround. |
@stargriv Do you use the latest Mac OS Sierra? I thought that there wouldn't exist such a folder named "X11R6". It should be renamed to "X11", I think (at least on my Mac that's the case). |
yup, can't create that folder. Is there a way to specifiy a folder to look for ssh-askpass |
@welljsjs Yes, I'm using the Sierra too and I have /usr/X11R6, which points to /opt/X11. |
@stargriv Hmm, I just installed the latest XQuartz version and see - there now is a directory named "X11R6", but still no ssh-askpass although I installed it via homebrew. Seems to work now - still not very as the user shouldn't have to do something like that. |
@welljsjs Did you linked ssh-askpass with: |
My steps that worked for me:
|
I think the issue that we can't seem to create the X11R6 folder, even with root, so we can't create the symlink in the folder. |
@tiny-cababge That's partly correct; see my comment above; the X11R6 folder definitely is created when you install the latest version of XQuartz. Then you're also able to create the symbolic link. |
Another addition for those who are using ssh keys:
More information regarding Sierra and ssh agent here |
To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed. It appears this issue already has a lot of workarounds, so let's rely on those! Thanks for your understanding. Happy coding! |
Steps to Reproduce:
Updating brew, installing the ssh-akspass package and starting the service didn't help.
The problem / bug seems to be only on OS X devices, haven't seen any reports about Windows so far.
Reproduces without extensions: Yes
The text was updated successfully, but these errors were encountered: