blocks|key|3024867|text|我终于找到了解决这个问题的办法。正如here所描述的，我在终端中运行了以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3024868|++unset+SSH_ASKPASS|code-block|syntax|javascript|3024869|然后运行git+push+origin+master就像它应该运行的那样。您还可以将该行添加到.bashrc文件中。|style|CODE|3024870|entityMap|0|LINK|mutability|MUTABLE|url|http://kartzontech.blogspot.it/2011/04/how-to-disable-gnome-ssh-askpass.html^0|I|4|0|0|0|4|M|1B|7|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$A|10|B|11|K|L]|$A|12|B|13|K|L]]|9|@]|C|$]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

I have finally discovered a solution to the problem. As it was described <a href="http://kartzontech.blogspot.it/2011/04/how-to-disable-gnome-ssh-askpass.html">here</a>, I ran the following command in the terminal:

<pre><code> unset SSH_ASKPASS
</code></pre>

and then running <code>git push origin master</code> works the way it should. You can also add the line to your <code>.bashrc</code> file.

blocks|key|190572|text|我最近在Git5机器上处理了这个问题，我们的RedHat版本是1.7.4.1。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|190573|我对unset+SSH_ASKPASS不会产生意想不到的后果没有很高的信心，所以我想看看是否有其他解决方案。|offset|length|style|CODE|190574|我不能确定，但似乎是在我们的patch+for+this+problem+was+in+the+works版本发布的同一时间。因此，在我看来，希望更新的版本可以纠正这种行为是合理的。|190575|它确实做到了。升级到Git1.8分支解决了这个问题。由于某种奇怪的原因，错误消息仍然显示，但系统会正确地提示您输入密码，并允许您继续。|BOLD|190576|entityMap|0|LINK|mutability|MUTABLE|url|http://git.661346.n2.nabble.com/git-calls-SSH-ASKPASS-even-if-DISPLAY-is-not-set-td5825303.html^0|0|2|H|0|E|13|0|0|7|J|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|J|3|K|5|6|7|12|8|@$D|13|E|14|F|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I recently dealt with this behavior on a RedHat 5 machine where our Git version was 1.7.4.1.

I didn't have a high degree of confidence that <code>unset SSH_ASKPASS</code> wouldn't have unintended consequences, so I wanted to see if there was another solution.

I couldn't tell for certain, but it seems that a <a href="http://git.661346.n2.nabble.com/git-calls-SSH-ASKPASS-even-if-DISPLAY-is-not-set-td5825303.html" rel="noreferrer">patch for this problem was in the works</a> around the same time that our version of Git had been published. So, it seemed to me that it was reasonable to hope that a more recent version would correct the behavior.

And indeed it did. Upgrading to the 1.8 branch of Git resolved the problem. The error message is still displayed for some odd reason, but you are correctly prompted for your password and allowed to continue.

blocks|key|3024895|text|这些答案对我都不起作用(通过Windows10上的Cygwin进入RHEL6.8服务器，并试图从RHEL箱克隆一个github.com存储库)，所以我所做的是通过SSH键而不是HTTPS用户名/密码进行克隆。例如，我使用git@github.com:MyUsername/myproject.git而不是https+url。我还适当地将我的公钥上传到Github中。这种方法工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3024896|注意:在上面的解决方案中，我实际上并没有尝试升级到git的1.8分支|3024897|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

None of these answers worked for me (ssh'ing via Cygwin on Windows 10 into a RHEL 6.8 server and trying to clone a github.com repo from the RHEL box) so what I did was clone via an SSH key rather than HTTPS username/password. e.g. I used git@github.com:MyUsername/myproject.git rather than the https url. I also appropriately uploaded my public key into Github. This method worked fine.

Note: Of the above solutions, I actually didn't try upgrading to the 1.8 branch of git

blocks|key|188835|text|您还可以尝试使用ssh+-Y登录到远程服务器，以便以图形方式显示对话框。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|188836|与OP一样，通过ssh+-X登录也不起作用。当尝试推送时，服务器只是重复了相同的错误消息-+(gnome-ssh-askpass:29241):+Gtk-WARNING+**:+cannot+open+display:+-就像它在没有X11转发的情况下通过ssh登录时所做的那样。这与OP在尝试ssh+-X时报告的行为略有不同，因为他的错误消息与仅使用ssh略有不同。|offset|length|style|CODE|188837|但是，对我来说，使用ssh+-Y登录后:没有错误，弹出密码对话框，我输入密码，GitHub接受推送。|188838|作为一个警告，当您将远程服务器视为受信任的客户端(https://askubuntu.com/questions/35512/what-is-the-difference-between-ssh-y-trusted-x11-forwarding-and-ssh-x-u)时，ssh+-Y可能会引发安全问题。因此，在使用它时要小心。|188839|entityMap|0|LINK|mutability|MUTABLE|url|https://askubuntu.com/questions/35512/what-is-the-difference-between-ssh-y-trusted-x11-forwarding-and-ssh-x-u^0|0|1A|1R|0|0|P|31|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

You can also try to login using ssh -Y to the remote server so the dialogue box can appear graphically. 

Like the OP, logging in via ssh -X didn't work. When trying to push, the server simply repeated the same error message - <code>(gnome-ssh-askpass:29241): Gtk-WARNING **: cannot open display:</code> - as it did when logging via ssh with no X11 forwarding. This is slightly different behavior from what the OP reported when he tried ssh -X as his error message changed slightly from just using ssh. 

However, for me, once logged in using ssh -Y: there was no error, the password dialogue box popped up, I typed the password in, and GitHub accepted the push. 

As a forewarning, ssh -Y can open up security problems as you are treating the remote server as a trusted client (<a href="https://askubuntu.com/questions/35512/what-is-the-difference-between-ssh-y-trusted-x11-forwarding-and-ssh-x-u">https://askubuntu.com/questions/35512/what-is-the-difference-between-ssh-y-trusted-x11-forwarding-and-ssh-x-u</a>). So be careful when using it.

I've been working on my project remotely through the command line on a machine to which I don't have admin rights and after running <code>git push origin master</code> I get the following error message:

<pre><code>(gnome-ssh-askpass:29241): Gtk-WARNING **: cannot open display:
</code></pre>

My <code>.git/config</code> file has the following contents:

<blockquote>
<pre><code> [core]
 repositoryformatversion = 0
 filemode = true
 bare = false
 logallrefupdates = true 
 [remote "origin"]
 fetch = +refs/heads/*:refs/remotes/origin/*
 url = https://username@github.com/username/repository.git 
 [branch "master"]
 remote = origin
 merge = refs/heads/master
</code></pre>
</blockquote>

I was getting the 403 error earlier. Following the comment <a href="https://stackoverflow.com/questions/7438313/pushing-to-git-returning-error-code-403-fatal-http-request-failed/9575906#9575906">here</a>, I put my username before the @ sign in the remote url and since then, I've been getting the Gtk error.

When I login to the machine using <code>ssh -X</code> and try to push, I get the following error:

<pre><code>X11 connection rejected because of wrong authentication.
(gnome-ssh-askpass:31922): Gtk-WARNING **: cannot open display:localhost:10.0
</code></pre>

If I change the url of the remote to <code>git@github.com:username/repository.git</code>, then the error is:

<pre><code>ssh: connect to host github.com port 22: Connection timed out
fatal: The remote end hung up unexpectedly
</code></pre>

Do you know how to fix this?

git produces Gtk-WARNING: cannot open display

服务器

GitHub

我一直在一台我没有管理员权限的机器上通过命令行远程处理我的项目，在运行git push origin master之后，我得到了以下错误消息：(gnome-ssh-askpass:29241): Gtk-WARNING **: cannot open display:我的.git/config文件包含以下内容： [co...

问git生成Gtk-警告:无法打开显示
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git生成Gtk-警告:无法打开显示EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git生成Gtk-警告:无法打开显示
EN