Skip to content
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

Error when ssh-ing #240

Closed
RobertAudi opened this issue Mar 11, 2011 · 8 comments
Closed

Error when ssh-ing #240

RobertAudi opened this issue Mar 11, 2011 · 8 comments

Comments

@RobertAudi
Copy link

When I ssh to my linode vps I get the following error:

Error: Can't open display: (null)

If I stop using oh-my-zsh the error disapears...

@blueyed
Copy link
Contributor

blueyed commented Mar 12, 2011

IIRC you have asked in #zsh about this too. Could this be solved?
Otherwise, please provide any additional info that might have came up. Thanks.

@RobertAudi
Copy link
Author

I don't know but this issue is definitely caused in some way by oh-my-zsh. The first step would be to locate the source of the error before even thinking of a solution imho.

@sorin-ionescu
Copy link
Contributor

This might be caused by alias ssh='ssh -X'. There is no X Server on your VPS. Deleting the alias should fix this.

@RobertAudi
Copy link
Author

@sorin-ionescu I just checked and ssh is not aliased. So that's not the problem...

@sorin-ionescu
Copy link
Contributor

Check the SSH configuration files as well. It sounds like it's trying to start the X Server.

On Sep 15, 2011, at 10:20, Aziz Lightreply@reply.github.com wrote:

@sorin-ionescu I just checked and ssh is not aliased. So that's not the problem...

Reply to this email directly or view it on GitHub:
#240 (comment)

@RobertAudi
Copy link
Author

I checked all the SSH config files that I know of (/etc/ssh/ssh_config and /etc/ssh/sshd_config on my VPS and on my Mac) and I found the following two lines in sshd_config on my VPS:

X11Forwarding yes
X11DisplayOffset 10

I then created the file ~/.ssh/sshd_config on my VPS and added to it the following:

X11Forwarding no

But that didn't fix the problem.

@sorin-ionescu
Copy link
Contributor

Do you have export DISPLAY=:0.0 by any chance? Google the error message.

Anyway, this is not an OMZ issue, but a ssh-agent issue and should be closed.

@RobertAudi
Copy link
Author

ok I found the problem. It was coming from an alias I had set in the git plugin. The alias used xclip which uses X's clipboard. Removing that alias made the error message disappear. The moral is, don't use xclip in OMZ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants