Disclaimer: All information is provided \"AS IS\" without warranty of any kind. Is there any way to disable that? You set the value in this manner: who -muR Joined: Wed Feb 22, 2017 3:08 pm. 6.490367 frames/sec - 6.728174 Mpixels/sec Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server xterm Xt error: Can't open display: love.dial.xs4all.nl:0.0 The client could make a connection to the server, but the server does not allow the client to use it (not authorized). On Node 0, vglrun crutserver & On Node 0, vglrun crserver; 13.4 A Note About Performance. If you see a value that's lower than 10¹, then something is interfering with the normal X11 forwarding set up by ssh, at least by overriding DISPLAY. X is obviously started on the main machine and I can launch Firefox and etc. I think it is something very simple and basic. If you are not using a graphical environment (i.e. Xhost still fucked. 13.273729 frames/sec - 13.760078 Mpixels/sec 3. , 并ä¸ä½¿ç¨å½ä»¤. 最近在WIN XP上安装了Xmanager用做X服务器，在Ubuntu Server 9.10上设置了DISPLAY环境变量（使其=运行Xmanager的WIN XP的IP:0.0）结果Xmanager套件里的xstart可以通过SSH开启一个xterm窗口，但在Ubuntu的终端里直接运行xterm就报"Can not open display"。另外，在xstart里用telnet协议 Pl. 13.051807 frames/sec - 13.530025 Mpixels/sec An X program needs two pieces of information in order to connect to an X display. -display is used to specify the 3D X server, whereas :50 is the 2D X server in your case. This is known as a "display server" and is probably your PC. The functional server gives a lot of output and seems fine when do xdpyinfo -display :0. 6.139027 frames/sec - 6.363961 Mpixels/sec Run a client on remote computer: "xclock" for example The above has worked in the past but now I get the following message on local Centos box: Error: Can't open display: Is ssh the problem? 6.214130 frames/sec - 6.441815 Mpixels/sec, I am using a google cloud instance, output of uname -a . OpenGL Renderer: Gallium 0.4 on llvmpipe (LLVM 3.9, 256 bits) In general, I cannot launch any x window programs. Error: Can't open display: :0.0 这是因为Xserver默认情况下不允许别的用户的图形程序的图形显示在当前屏幕上. 6.854301 frames/sec - 7.105443 Mpixels/sec 6.832524 frames/sec - 7.082868 Mpixels/sec Please contact me if anything is amiss at Roel D.OT VandePaar A.T gmail.com Now, run the xvfb service at a custom display number, like: sudo Xvfb :5. X-Server can not be started on display :0 Good Morning, I recently cloned a sunblade 2500 to another sunblade 2500 and had an issue getting the GUI: X-Server can not be started on display :0 The issue was that the first machine had an xvr600 graphics card, and the new machine had an xvr100. export DISPLAY=:0.0 startxfce4 it gives this /usr/bin/startxfce4: X server already running on display :0.0 xrdb: Connection refused xrdb: Can't open display ':0.0' Unable to init server: Could not connect: Connection refused xfce4-session: Cannot open display: . First of all, you didn't specify if you have a desktop environment (or X) installed on your server? Edit: Removing `-nolisten tcp` did nothing noticeable. For example: venkat@home-laptop:~/Downloads/$ ps -eaf | grep vnc venkat 3504 1 0 ⦠So any OpenGL program needs to be launched with vglrun to make use of OpenGL. -(deb) sudo apt install libglew-dev Make sure you are running any GUI process from the same user where vncserver process is owned by. 3.986369 frames/sec - 4.132429 Mpixels/sec Period. /etc/opt/VirtualGL/vgl_xauth_key does nor exist after I ran the configuration with YYYX. thanx xyz 6.908684 frames/sec - 7.161818 Mpixels/sec thanx xyz Answering no will cause GDM to attempt starting the server on :0 again. 11.793930 frames/sec - 12.226060 Mpixels/sec Error: cannot open display: :0.0. :0 should work as should :0.0 (normal default) as also localhost:0 etc. But not for X11. The best thing to do is: - kill the window system Follow the first answer on here: The existing answers fail to address the broader picture. 2./opt/VirtualGL/bin/glxspheres64 Open GUI applications in that host. Re: ssh -Y, gedit, Could not connect, cannot open display. Get it working using an X11 configuration tool of your choice and then go back to run gnuplot. By clicking “Sign up for GitHub”, you agree to our terms of service and Set DISPLAY environment variable: export DISPLAY=:0.0 4. (ä¾å¦:xshell)è¿å»,è¿è¡å¾å½¢çé¢çç¨åº,å¦æ没æ设置,ç³»ç»æ¯ä¸å 许ç¨åºå¯å¨çã I was able to start firefox when I remotely logged into another server: myserver2. I am trying to use using TurboVNC with VirtualGL(2.6.2_amd64). Not a valid configuration. If you still get the âcannot open displayâ error, set the DISPLAY variable as shown below. I have not yet install mesa-dev, because I am not sure whether it will cause more problems. when ever i am trying to open a game it says this only... even the sounds come but it is not opening,on a black screen,the above given message is displayed,when press ok,the sounds come but the home screen opens up. GLX FB config ID of window: 0xa1 (8/8/8/0) root 10274 0.0 0.1 3956 628 tty9 Ss+ 06:33 0:00 -sh -c /usr/bin/whiptail --yesno 'There already appears to be an X server running on display :0. It is a much more meaningful benchmark, and it also displays the OpenGL renderer string, which allows you to verify whether the GPU is being used. 14.920510 frames/sec - 15.467197 Mpixels/sec The address of the display is normally indicated in the DISPLAY environment variable. Security is not an issue. 8.593932 frames/sec - 8.908814 Mpixels/sec On Node 0, vglrun crutserver & On Node 0, vglrun crserver; 13.4 A Note About Performance. In contrast to other display servers Xvfb performs all graphical operations in memory without showing any screen output. xhost: unable to open display "practice.ol75.com:0.0" You can see I tried everything I could think of but it failed and failed again. 8.705185 frames/sec - 9.024143 Mpixels/sec Have a question about this project? 9.581499 frames/sec - 9.932565 Mpixels/sec Run a client on remote computer: "xclock" for example The above has worked in the past but now I get the following message on local Centos box: Error: Can't open display: Is ssh the problem? I have a VcXsrv running. If you still get the âcannot open displayâ error, set the DISPLAY variable as shown below. It assumes a very fast connection between the X server and the Chromium Server. reboot the machine, directly start a vncserver and ; connect to it with a client, no OpenGL application is working and I get the error 5.815673 frames/sec - 6.028759 Mpixels/sec I am running 'export DISPLAY=:1' same as my vncserver the then 'vglrun glxgears -display :1 ', however it shows: [VGL] ERROR: Could not open display :0. 3.955810 frames/sec - 4.100751 Mpixels/sec So I guess the 3D X server is not running. $ export DISPLAY='IP:0.0' 6.713118 frames/sec - 6.959087 Mpixels/sec -(mac) sudo port install glew The xhost command fails because you have not set the DISPLAY value. I am attempting to open an xwindow app ( like xterm) remotely on a newly built rhel7.4 Enterprise Linux Desktop machine. 6.741568 frames/sec - 6.988579 Mpixels/sec In other words: If I . On the remote machine: export DISPLAY=newrhel74desktop:0 xterm Return = xterm Xt error: Can't open display Have tried the obvious: xhost + ( on the newrhel74desktop machine) updated : in /etc/ssh/sshd_config X11Forwarding yes X11DisplayOffset 10 X11UseLocalhost no 10.387560 frames/sec - 10.768160 Mpixels/sec help because what you wrote _should_ just work tell us more about _your_ situation: - operating system and version in use - desktop environment (if applicable) in use - VM (if applicable) in use You signed in with another tab or window. You can also check the complete Environment Variables for the User using the below mentioned command where you will find the entry for the DISPLAY, else, so it autimatically finds some available X display number and uses it. @SSJCarti said in qt.qpa.xcb: could not connect to display :0:. 3. This could be one of the reasons you could get the following error: Invalid MIT-MAGIC-COOKIE-1 keyError: Can't open display: :1. Visual ID of window: 0x1ea root 10280 0.0 0.3 17904 1608 tty9 S+ 06:33 0:00 /usr/bin/whiptail --yesno There already appears to be an X server running on display :0. Nothing to do with gnuplot. more info, and to (temporarely) disable both firewalls. 5.253095 frames/sec - 5.445568 Mpixels/sec DISPLAY를 아래와 같이 설정해도 똑같은 결과가 나옵니다 #export DISPLAY=:0.0 #xmodmap No protocol specified xmodmap: unable to open display ':0.0' … This is localhost in a normal terminal window. You definitely want VGL_DISPLAY/'vglrun -display' to be pointing to :0, which is the default. Successfully merging a pull request may close this issue. Last edited by lubiebudyn (2010-11-19 19:24:35) Offline #2 2010-11-19 19:01:29. I added passwords to students with sudo passwd username After that, I tried to get into user environment by using ssh username@ip, then I did who and saw the :0 or :1 as a display number. All other sanity checks can be executed without an error message. privacy statement. Check which address your VcXSrv is listening, by hover the tray icon of VcXSrv, it could be hostname:x.0 and you should check x is 0. [VGL] ERROR: Could not open display :0. Trademarks are property of their respective owners. The non-working server gives the output, for xdpyinfo -display :0, xdpyinfo: unable to open display ":0". 8.812639 frames/sec - 9.135534 Mpixels/sec This works like a charm but only if I log myself in on DISPLAY 0 and launch at least one OpenGL application beforehand. weixin_34095889çå客. Polygons in scene: 62464 (61 spheres * 1024 polys/spheres) | Content (except music \u0026 images) licensed under CC BY-SA https://meta.stackexchange.com/help/licensing | Music: https://www.bensound.com/licensing | Images: https://stocksnap.io/license \u0026 others | With thanks to user Woltan (serverfault.com/users/129979), and the Stack Exchange Network (serverfault.com/questions/947880). In bash for Windows, setting the DISPLAY environment variable allows WSL programs to use the Windows GUI. Not a valid configuration. VirtualGL has a script called > vglserver_config that is used to configure the server to allow access to > display :0 when the server is sitting at the login prompt. 5.950129 frames/sec - 6.168141 Mpixels/sec The problem is that something isn't configured properly vis-a-vis allowing access to :0. Xwindows is a very special environment and it starts with the DISPLAY value being set to the IP address of your display device. DevOps & SysAdmins: Why does VirtualGL raise a *Could not open display :0* error after host reboot?Helpful? Already on GitHub? Should another display number by tried? Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display ':0' I have conducted extensive research into this matter and have already tried the following suggested procedure to no avail: Used "xauth list" to get the MIT-MAGIC-COOKIE-1 value for my local host's display. First, install xvfb on your server. Thanks, sudo nvidia-xconfig -a --allow-empty-initial-configuration --use-display-device=None \ --virtual=1920x1200 --busid {busid} and re-run vgl configure script did the work for me. Open GUI applications in that host. 6.352117 frames/sec - 6.584858 Mpixels/sec Reinstalling "virt-manager" didn't bring any good. So for me, ssh -X was just being ignored altogether Context is Indirect Yes, 'root' is the supreme God of your system and is omni potent. It assumes a very fast connection between the 2D X server and the Chromium Server. Post. According to this site:. The DISPLAY variable is suspicious. Yes, 'root' is the supreme God of your system and is omni potent. Used "export DISPLAY=:0" on the remote host. when you're logged in remotely (but the number can change depending on how many X connections are active). export DISPLAY=:0.0 ï¼ï¼ï¼è¿å¥è¯å¯ä»¥åè¿.bashrcï¼ è®¾ç½®DISPLAYç¯å¢åé, è¿è¡å¾å½¢ç¨åº(å¦xclock)æ¶ä¼æ¶å°å¦ä¸é误: Xlib: connection to ":0.0" refused by server Xlib: No protocol specified. 11.716695 frames/sec - 12.145994 Mpixels/sec We’ll occasionally send you account related emails. ...in the shell output, then this means that the 3D-capable X server on the server side (that is supposed to handle the OpenGL rendering) is either not running, or not properly set up for use with VirtualGL (see Installation and setup), or VGL_DISPLAY is not set correctly (see Running Applications). [VGL] ERROR: Could not open display :0. 11.918804 frames/sec - 12.355509 Mpixels/sec VcXsrv makes it possible to run Linux GUI programs installed with WSL, the Windows Subsystem for Linux. Error: cannot open display: localhost:0.0 To setup the display I used the command $ export DISPLAY=localhost:0.0 Some site suggested using the following, but it didn't work either: $ export DISPLAY=:0.0 I am using PuTTY and I have the Enable X11 forwarding check box checked and XMing is running on Windows. Regardless of that, you can achieve headless setup for your spider by using xvfb:. The best thing to do is: - kill the window system - log off the terminal - log on as root - startx - do your thing You will HAVE to start X11 as user 'root'. If ssh is able to establish the connection, it will set DISPLAY to the proper value. The vglserver_config script only supports specific Linux distributions, so I need to know which Linux distribution you are using in order to diagnose the problem. 1 post views Thread by Jeremy C. Reed | last post: by Python I strongly suspect that you are mis-reporting something. My earlier ssh connection did not request X11Firwarding, therefore future ssh call's options weren't being used. For instance, if VcXsrv is configured to use display number zero, the command DISPLAY=:0 etr would run the game Extreme Tux Racer Given that you're running VcXsrv, you may need to double check its configuration and what display it's exporting/providing to the Linux side of the Windows WSL (sorry but I don't have experience with Windows WSL to help more). when you're logged in remotely (but the number can change depending on how many X connections are active).The address of the display is normally indicated in the DISPLAY environment variable. The python bindings for gconf (gnome-python2-gconf) could not be found. Still at previous "No protocol .... cannot open display :0". This virtual server does not require the computer it is running on to even have a screen or any input device. Linux sbsy-vm 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux. Since you have X11DisplayOffset set to 10 (the default value), ssh will use the first available display starting at 10. I can't imagine any scenario in which the sanity checks mentioned at https://cdn.rawgit.com/VirtualGL/virtualgl/2.6.2/doc/index.html#hd006002001 work but VirtualGL still fails to access the 3D X server. xhost: unable to open display "localhost:0.0" There are three phenomena I want to mention. $ export DISPLAY='IP:0.0' Logged into the remote host via ssh. Xwindows is a very special environment and it starts with the DISPLAY value being set to the IP address of your display device. This is known as a "display server" and is probably your PC. [VGL] Could not open display (null). 12.883871 frames/sec - 13.355936 Mpixels/sec When you run in an X11 environment, the environmental variable DISPLAY must be set to a valid X display. by tunk » Sat Dec 07, 2019 4:02 pm. -display is used to specify the 3D X server, whereas :50 is the 2D X server in your case. ~$ gksu gparted (gpartedbin:24252): Gtk-WARNING **: cannot open display: :0 The same happens with gparted-pkexec: ~$ gparted-pkexec No protocol specified (gpartedbin:25454): Gtk-WARNING **: cannot open display: :0 What could possibly be causing this? firefox is just an example. It needs the password for the display. Security is not an issue. I'm on a local network. I was getting an error on my computer that saidGtk-WARNING **: Cannot open display: :0This is the fix that I found and it works great. The text was updated successfully, but these errors were encountered: You are able to run GLXgears directly because TurboVNC has a built-in software-only OpenGL implementation, but if you run an OpenGL application in TurboVNC without VirtualGL, that application will not use the GPU. Type 'xfce4-session - … I need to build it and it requires: another user of mydesktop is able to start firefox after logging into myserver. > **(gnomesu:3218):WARNING**: Could not open X display > > How I can open /etc/sysctl.conf for editing. cannot open Display settings after windows 10 update, get "This file does not have a program associated with it for performing this action" Windows 10 did an upgrade last night without asking me or warning me, which is unacceptable for a critical work machine. But not for X11. Set DISPLAY environment variable: export DISPLAY=:0.0 4. I provide that configuration assistance only as a paid service, but I can tell you that the major differences between a GCP VirtualGL configuration and an ordinary VirtualGL configuration are: If the advice above is insufficient to make VirtualGL work with your GCP instance, then you will need to pay me to produce a configuration procedure for that specific instance. However, I can directly run glxgears successfully. Should another display number by tried? xhost +SI:localuser:root which will allow the root user to display applications on your desktop. _tkinter.TclError: couldn't connect to display "192.168.1.9:0.0" ã¿ã¼ããã«ã®ä¸é¨ã«æ¬¡ã®æã表示ããã¦ãã¾ãã xhost: unable to open display "0.0" â解決ãã¾ããã ã¾ãããã£ã¹ãã¬ã¤0.0ãéããããã«ããªãã¨ãããªãã§ãããã ãããããã®ããæ¹ããããã¾ããã Please use GLXspheres instead of GLXgears. оваÑелей и 1 ÐоÑÑÑ Ð¿ÑоÑмаÑÑиваÑÑ ÑÑÑ ÑемÑ. Also check if X11Forwarding is enabled in /etc/ssh/sshd_config. Glew If you do have an X server running but have switched to a tty (for example by pressing Ctrl + Alt + F1 ), you might simply need to return to your graphical environment. So if that fails it's probably xauth. The problem is caused by user 'you' owning the display and then user 'root' wanting to get away with it. 3. However, Google Cloud instances require additional configuration in order to make them work with VirtualGL. 5.661016 frames/sec - 5.868435 Mpixels/sec I fixed the problem. When using the VGL Transport, SSH X11 tunneling is normally necessary with modern operating systems, because most of them do not allow TCP connections to the X server by default. Most likely for remote server you X is not :0.0, but something else (usually :10.0); although your XMing is considering itself to be :0.0, PuTTY does port-forwarding magic to hide that, since :0.0 might be alredy taken by other user or default X or smth. (Debian 10 "Buster" has not been tested, to my knowledge. Refer to https://virtualgl.org/Documentation/OSSupport.) As a workaround until the application is updated, you can run. Chromium’s use of X11 is generally not very optimal. I'm on a local network. Re: Error: cannot open display: :0.0 [SOLVED] Try either : export DISPLAY=":0.0" or . Answering no will cause GDM to attempt starting the server on :0 again. 6.754384 frames/sec - 7.001864 Mpixels/sec It needs the address of the display, which is typically :0 when you're logged in locally or :10, :11, etc. Contact me through e-mail if you are interested in pursuing that: https://virtualgl.org/About/Contact. I am not running this through SSH or VNC. Assuming you are using apt-get: sudo apt-get install xvfb. In this case, null indicates that the VirtualGL display or device specification was "" (a null string, which is the VirtualGL default, ⦠DevOps & SysAdmins: Why does VirtualGL raise a *Could not open display :0* error after host reboot?Helpful? Re: ssh -Y, gedit, Could not connect, cannot open display Post by tunk » Sat Dec 07, 2019 9:54 pm I don't know if it will make any difference, but you could try "ssh -X" instead of "ssh -Y". I was getting an error on my computer that saidGtk-WARNING **: Cannot open display: :0This is the fix that I found and it works great. I do that work for a flat fee. The xhost command fails because you have not set the DISPLAY value. Please support me on Patreon: https://www.patreon.com/roelvandepaarWith thanks \u0026 praise to God, and with thanks to the many people who have made this project possible! However, in > VirtualGL 2.1, that script did not properly handle Ubuntu systems. xhost +your-username. 5.800145 frames/sec - 6.012662 Mpixels/sec ...in the shell output, then this means that the 3D-capable X server on the server side (that is supposed to handle the OpenGL rendering) is either not running, or not properly set up for use with VirtualGL (see Installation and setup), or VGL_DISPLAY is not set correctly (see Running Applications). Your's is apparently set to blank, or doesn't exit at all. I think it might be the `-nolisten tcp` and I'll try that next. The problem is caused by user 'you' owning the display and then user 'root' wanting to get away with it. Cheers! OpenGL GLX extension not supported by display ':0.0' I'm using Fedora Core 3 and in my /etc/X11/xorg.conf does contain the following lines before I … Any help would be appreciated. However, I can directly run glxgears successfully. to your account. Error: Can't open display: 172.30.96.1:0.0 after a few seconds. If running Ubuntu 17.10 or newer, this issue can arise when an application has not been updated with full support for Wayland. In certain modes, Chromium polls the X server on every frame to determine whether windows have been resized, etc. [root@rakcal ~]# virt-viewer winxp1 Cannot open display: Run 'virt-viewer --help' to see a full list of available command line options Does anyone know what might be the problem or if I'm missing anything? ! On Node 0, launch crappfaker (do not use vglrun here) Again, it’s always a good idea to make sure this works without VirtualGL before adding VirtualGL … https://cdn.rawgit.com/VirtualGL/virtualgl/2.6.2/doc/index.html#hd006002001, https://virtualgl.org/Documentation/OSSupport, https://cloud.google.com/compute/docs/gpus/add-gpus#installing_grid_drivers_for_virtual_workstations, https://virtualgl.org/Documentation/HeadlessNV, The need to use a specific Google-supplied build of the nVidia drivers (, The need to configure the X server as headless (, The need to install and enable a display manager (GDM, LightDM, etc. Normally DISPLAY should be set to localhost:n.0 (where n is a display number chosen by the SSH server) when using SSH X11 tunneling. 6.317764 frames/sec - 6.549247 Mpixels/sec Try disabling xhost with: xhost + (This is unlikely to work but easier to do than the following which is required if it didn't). After opening ssh connection to the remote host as explained above, you can open any GUI application which will open it without any issue. 8.666726 frames/sec - 8.984275 Mpixels/sec In certain modes, Chromium polls the 2D X server on every frame to determine whether windows have been resized, etc. 6.613416 frames/sec - 6.855732 Mpixels/sec virtualgl ããã±ã¼ã¸ãã¤ã³ã¹ãã¼ã«ã㦠ãã¡ã ã®æé ã«å¾ã£ã¦è¨å®ãã¦ãã ãããArch ã§ã¯ /opt/VirtualGL/bin/vglserver_config 㨠/opt/VirtualGL/bin/glxinfoã¯ãã ã® vglserver_config 㨠vglxinfo ã§ãã Sign up for a free GitHub account to open an issue and contact its maintainers and the community. (Pardon my excitement) I used this website.. you are logging in on the system console with no windows etc; or you are logging in remotely from a text-only terminal over SSH or similar, such as from a Windows computer running PuTTY) then no GUI is involved, and DISPLAY will typically be unset. It needs the address of the display, which is typically :0 when you're logged in locally or :10, :11, etc. /etc/opt/VirtualGL/vgl_xauth_key does nor exist after I ran the configuration with YYYX. You could try to add the "-v" option to see if that gives you. Is there any way to disable that? I am running 'export DISPLAY=:1' same as my vncserver the then 'vglrun glxgears -display :1 ', however it shows: [VGL] ERROR: Could not open display :0. -(lin) sudo apt install libgl1-mesa-dev there perfectly, but still not under SSH. 9.466578 frames/sec - 9.813433 Mpixels/sec On Node 0, vglrun crserver & On Node 0, set VGL_GLLIB to the location of the “real” libGL (example: /usr/lib/libGL.so.1 or /usr/lib64/libGL.so.1). 13.778510 frames/sec - 14.283355 Mpixels/sec Chromium’s use of X11 is generally not very optimal. You set the value in this manner: who -muR Sign in PrivateLooms Member Registered: 2010-11-19 Posts: 5. Permissions are most likely problem. You are responsible for your own actions. The first line of the sanity check is xauth merge /etc/opt/VirtualGL/vgl_xauth_key, which would fail if /etc/opt/VirtualGL/vgl_xauth_key does not exist. OpenGL (Desktop / ES / ES2) I used export DISPLAY=:0 or :1 then I ran xeyes command and HEYYYYYYY, IT WORKED! export DISPLAY=:0.0 You can then run your GUI program normally. ç´æ¥ç»éå¾å½¢çé¢æè ç»éå½ä»¤è¡çé¢å使ç¨start x å¯å¨å¾å½¢, DISPLAY ç¯å¢åéå°èªå¨è®¾ç½®ä¸º:0:0, æ¤æ¶å¯ä»¥æå¼ç»ç«¯, è¾åºå¾å½¢ ç¨åº çå称 (æ¯å¦ x clock)æ¥å¯å¨ ç¨åº, å¾å½¢å°æ¾ç¤ºå¨æ¬å°çªå£ä¸, å¨ç»ç«¯ä¸è¾å ¥printenvæ¥çå½åç¯å¢åé, è¾åºç»æä¸æå¦ä¸å 容: DISPLAY =:0.0. æ¬æºè¿è¡xç¨åºåºç° ï¼Can't open display åå åå ¶ 解å³æ¹æ³ ï¼è²ä¼¼éæ°¸ä¹ ï¼. P.S My task is based on . You appear to be running Debian 9 ("Stretch"), which should work with VirtualGL. ). The other sanity checks run without outputing error messages. DevOps \u0026 SysAdmins: Why does VirtualGL raise a *Could not open display :0* error after host reboot?Helpful? 6.492184 frames/sec - 6.730058 Mpixels/sec After opening ssh connection to the remote host as explained above, you can open any GUI application which will open it without any issue. Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. Thanks for all advices. The text was updated successfully, but these errors were encountered: Copy link luochen1990 commented Nov 2, 2020. It gave me a hint about what to do next. -(win) built automatically (assuming git is on your path) You are correct, xauth merge /etc/opt/VirtualGL/vgl_xauth_key fails because the file does not exists.