# Could not initialize GLX with NVIDIA 384.66 on Ubuntu 16.04 **URL:** \ **Category:** Linux\ **Created:** [August 30, 2017, 5:16pm UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012 "2017-08-30T17:16:25Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![williamvdk](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@williamvdk](https://forums.developer.nvidia.com/u/williamvdk)\ **Post date:** [August 30, 2017, 5:16pm UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012/1 "2017-08-30T17:16:25Z")
Hi, I’m running ubuntu 16.04 with three Titan X cards. I installed NVIDIA 384.66 driver as part of installing cuda via the following commands: ```auto sudo dpkg -i cuda-repo-ubuntu1604_8.0.61-1_amd64.deb sudo apt-get update sudo apt-get install cuda ``` I also followed the steps listed in this StackExchange answer: [https://askubuntu.com/a/457928/439653](https://askubuntu.com/a/457928/439653). However, when I run an X-Window application that uses GLX (Agisoft Photoscan, to be precise), I see the following output: ```auto Could not initialize GLX ``` Additionally, when I run glxgears, I see: ```auto Error: couldn't get an RGB, Double-buffered visual ``` (In both cases, the program crashes.) The above problems also occur with 3 1080Tis in another machine. Can someone help me fix this? Thanks. [nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/v8bNXGJa2o62E4Q9wiZaurYd15N.gz) (283 KB) ---
**Author:** ![generix](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/generix/32/16024_2.png) [@generix](https://forums.developer.nvidia.com/u/generix)\ **Post date:** [August 30, 2017, 7:14pm UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012/2 "2017-08-30T19:14:07Z")
Looks like you don’t have a monitor connected and use AllowEmptyInitialConfiguration to get the xserver started. This way, you don’t really get a (virtual) screen. Use option ConnectedMonitor to achieve that. ---
**Author:** ![aplattner](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/aplattner/32/14043_2.png) [@aplattner](https://forums.developer.nvidia.com/u/aplattner)\ **Post date:** [August 30, 2017, 7:20pm UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012/3 "2017-08-30T19:20:54Z")
You should still get GLX even with AllowEmptyInitialConfiguration. From the attached bug report, it looks like libglx is initializing correctly in the X server. Can you please attach the output of glxinfo from one of the X screens? Also please check that the correct client-side libGL is installed. The bug report script normally uses “ldd /usr/bin/glxinfo” to check this, but apparently you don’t have glxinfo installed. Are you trying to use indirect GLX, by any chance? ---
**Author:** ![williamvdk](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@williamvdk](https://forums.developer.nvidia.com/u/williamvdk)\ **Post date:** [August 30, 2017, 8:02pm UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012/4 "2017-08-30T20:02:20Z")
Here are some key outputs: ```auto $ glxinfo name of display: localhost:12.0 Error: couldn't find RGB GLX visual or fbconfig $ ldd /usr/bin/glxinfo linux-vdso.so.1 => (0x00007ffe475b3000) libGL.so.1 => /usr/lib/nvidia-384/libGL.so.1 (0x00007fec754ce000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fec75194000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fec74dc9000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fec74bc5000) libGLX.so.0 => /usr/lib/nvidia-384/libGLX.so.0 (0x00007fec74995000) libGLdispatch.so.0 => /usr/lib/nvidia-384/libGLdispatch.so.0 (0x00007fec746c6000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fec744a4000) /lib64/ld-linux-x86-64.so.2 (0x0000556b3d959000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fec74292000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fec7408d000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fec73e87000) ``` Perhaps I am trying indirect GLX? I’m not sure what that is. I’m running SSH -Y from a remote client. Is that the problem? ---
**Author:** ![bhupesh.c](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@bhupesh.c](https://forums.developer.nvidia.com/u/bhupesh.c)\ **Post date:** [December 26, 2017, 5:33am UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012/5 "2017-12-26T05:33:27Z")
Hello, I am facing the same issue as i have connected the UBUNTU server 16.04 via XRDP. root@ubuntu:/# glxinfo name of display: :11.0 Error: couldn’t find RGB GLX visual or fbconfig root@ubuntu:/# ldd /usr/bin/glxinfo linux-vdso.so.1 =\> (0x00007ffeb0b51000) libGL.so.1 =\> /usr/lib/x86\_64-linux-gnu/mesa/libGL.so.1 (0x00007f4beab58000) libX11.so.6 =\> /usr/lib/x86\_64-linux-gnu/libX11.so.6 (0x00007f4bea81e000) libc.so.6 =\> /lib/x86\_64-linux-gnu/libc.so.6 (0x00007f4bea454000) libexpat.so.1 =\> /lib/x86\_64-linux-gnu/libexpat.so.1 (0x00007f4bea22b000) libxcb-dri3.so.0 =\> /usr/lib/x86\_64-linux-gnu/libxcb-dri3.so.0 (0x00007f4bea028000) libxcb-present.so.0 =\> /usr/lib/x86\_64-linux-gnu/libxcb-present.so.0 (0x00007f4be9e25000) libxcb-sync.so.1 =\> /usr/lib/x86\_64-linux-gnu/libxcb-sync.so.1 (0x00007f4be9c1e000) libxshmfence.so.1 =\> /usr/lib/x86\_64-linux-gnu/libxshmfence.so.1 (0x00007f4be9a1b000) libglapi.so.0 =\> /usr/lib/x86\_64-linux-gnu/libglapi.so.0 (0x00007f4be97ec000) libXext.so.6 =\> /usr/lib/x86\_64-linux-gnu/libXext.so.6 (0x00007f4be95da000) libXdamage.so.1 =\> /usr/lib/x86\_64-linux-gnu/libXdamage.so.1 (0x00007f4be93d7000) libXfixes.so.3 =\> /usr/lib/x86\_64-linux-gnu/libXfixes.so.3 (0x00007f4be91d1000) libX11-xcb.so.1 =\> /usr/lib/x86\_64-linux-gnu/libX11-xcb.so.1 (0x00007f4be8fcf000) libxcb-glx.so.0 =\> /usr/lib/x86\_64-linux-gnu/libxcb-glx.so.0 (0x00007f4be8db6000) libxcb-dri2.so.0 =\> /usr/lib/x86\_64-linux-gnu/libxcb-dri2.so.0 (0x00007f4be8bb1000) libxcb.so.1 =\> /usr/lib/x86\_64-linux-gnu/libxcb.so.1 (0x00007f4be898f000) libXxf86vm.so.1 =\> /usr/lib/x86\_64-linux-gnu/libXxf86vm.so.1 (0x00007f4be8789000) libdrm.so.2 =\> /usr/lib/x86\_64-linux-gnu/libdrm.so.2 (0x00007f4be8578000) libm.so.6 =\> /lib/x86\_64-linux-gnu/libm.so.6 (0x00007f4be826f000) libpthread.so.0 =\> /lib/x86\_64-linux-gnu/libpthread.so.0 (0x00007f4be8052000) libdl.so.2 =\> /lib/x86\_64-linux-gnu/libdl.so.2 (0x00007f4be7e4e000) /lib64/ld-linux-x86-64.so.2 (0x00007f4beadca000) libXau.so.6 =\> /usr/lib/x86\_64-linux-gnu/libXau.so.6 (0x00007f4be7c4a000) libXdmcp.so.6 =\> /usr/lib/x86\_64-linux-gnu/libXdmcp.so.6 (0x00007f4be7a44000) Please provide me the solution if someone has the resolution. ---
**Author:** ![generix](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/generix/32/16024_2.png) [@generix](https://forums.developer.nvidia.com/u/generix)\ **Post date:** [December 27, 2017, 2:43pm UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012/6 "2017-12-27T14:43:51Z")
If you want a simple solution, set up a real X server then use x11vnc to connect. ---
**Author:** ![chemal](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@chemal](https://forums.developer.nvidia.com/u/chemal)\ **Post date:** [December 27, 2017, 6:50pm UTC](https://forums.developer.nvidia.com/t/could-not-initialize-glx-with-nvidia-384-66-on-ubuntu-16-04/53012/7 "2017-12-27T18:50:49Z")
@williamvdk: Try export \_\_GLX\_VENDOR\_LIBRARY\_NAME=nvidia before you start your program with indirect GLX.