-
Notifications
You must be signed in to change notification settings - Fork 90
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
dev-python/pyperclip-1.5.27 fails with "cannot connect to X server localhost:10.0" #144
Comments
The ebuild was copied from the dev-zero overlay, please join the following bug report: |
please make sure that your X env is not broken. You have multiple font warnings etc. I can not reproduce the bug using different env including a clean server (no X) |
I'm closing this bug for now. Please provide more details so that I could reproduce it. |
Maybe this helps? Is it a strict requirement to be running within a local X login for this package to build? I hope not, as that would be just silly... wdawson@pentoo $ ssh -Y 192.168.2.147
[1] "pentoo" /var/lib/layman/pentoo
/mnt/disk-image2/di 100%[===================>] 16.54K --.-KB/s in 0.02s 2017-01-22 09:50:45 (807 KB/s) - ‘/mnt/disk-image2/distfiles/pyperclip-1.5.27.zip’ saved [16938/16938]
|
Well, I tried to compile it on a remote box with no X, did not hit this problem. There is something special in your env.. |
I would have thought ssh with -Y option to be the same as -X option for this, but it isn't. So, definitely not an ebuild bug, but an "interesting" implementation difference in SSH command line options. That is, I was able to get this to work by logging in to my remote system using -X, but not with -Y. |
Sorry to necro, but for people landing here from Google like I did: Given the comment above that it seemed to work with untrusted X forwarding, I worked around this problem by adding |
@gh2k |
@blshkv according to the comments above, |
ok, I haven't used X forwarding for a long time and it seems like -X is more "secure". However, I was using "localhost" forwarding:
Could you also try this setup with -Y to see if it works? P.S. Also, see https://unix.stackexchange.com/questions/12755/how-to-forward-x-over-ssh-to-run-graphics-applications-remotely |
build.log and other files attached.
files.zip
The text was updated successfully, but these errors were encountered: