![]() Windows Subsystem for Linux (WSL) Has Same Error This issue no longer exists from Ubuntu 18.04 LTS. $ sudo rm /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Now I just needed to remove the library provided by mesa and everything worked perfectly. LibQtOpenGL.so.4 (libc6) => /usr/lib/i386-linux-gnu/libQtOpenGL.so.4 The output was something like: libwayland-egl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 To test this, you can run this command $ sudo ldconfig -p | grep -i gl.so When using XQuartz and ssh -Y, you should never need to manually set the DISPLAY environment variable, as XQuartz will set it on the Mac, and the ssh -Y will set it on the Linux system.For anyone still getting same error, if you are using nvidia driver, sometimes you will see that libGL.so.1 points to ambiguous libGL provided by both mesa and nvidia. If your macOS DISPLAY environment variable is really localhost:11.0, then either you are unintentionally setting the environment variable manually, or in your shell initialization scripts. The localhost:10.0 may be localhost:11.0, or localhost:12.0, etc. Your Linux DISPLAY environment variable should look similar to this: It would be correct for Linux after doing ssh -Y What you showed me should NOT be the macOS DISPLAY environment value. The leading 's' means it is a network 'socket' Srw-rw-rw- 1 raharris 0 Apr 15 12:10 /private/tmp//org.xquartz:0 The hFmzPYzDYa will be different for you, but the pattern should be the same. This is what your macOS DISPLAY environment variable should look like. Thanks again for your time and information. ![]() Have you tried something simply, such xclock?įinally, why are you using xterm, when you have a very good terminal emulator in Applications-> Utilities-> Terminal, or the open source iTerm2, which run native on the Mac?Īns: just for checking purpose. It is something I would associate with using host+, and counter productive to using ssh -Y Just to be sure, did your remote login shell scripts set its own DISPLAY environment variable. When using ssh -Y, you DO NOT need host+, and if anything, host+ might interfere. Xterm: Xt error: Can't open display: localhost:12.0 ![]() When you ssh -Y does the DISPLAY environment variable look similar to localhost:10.0 ?Ĭonnect localhost port 6011: Connection refused Please find my answers as mentioned below.Īns: Yes, my XQuartz version is "XQuartz 2.8.5 (xorg-server 21.1.6)"ĭid you reboot after installing, so that XQuartz sets up all the necessary hooks in your macOS login session? The day after, the problem was there again (same network). There is an additional particular that is driving me crazy: this problem appeared to be fixed few days ago, when I connected to a new network and the graphic was successfully displayed. However, I still cannot do it when I work in ssh and I couldn't find instructions about how to do this. I tried, and I could run the xclock and related commands from the Apple terminal. Regarding to this, I found an old post in this forum that suggested to set the DISPLAY variable as :0.0. In addition, I just realized that if I give the simple command "xclock" in the Apple terminal, it remains stuck as well. From that moment, when I connect to an ssh session and I try do some graphical display from the Apple terminal, the command just remains stuck after an empty line is printed. ![]() I am using macOS (Big Sur 11.4), everything was working well until I did an update of XQuartz (2.8.1). I am experiencing some troubles with X11. ![]() X11 not displaying when run in ssh session Hi, ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |