In vglserver_config, there is an option to grant 3D X server access to members of the vglusers group or to all users of the system. If you elect to grant access only to members of vglusers, then it will modify the display manager startup script to run vglgenkey, which generates vgl_xauth_key.
However, I'm noticing that you're using GDM rather than LightDM. There is a known issue that prevents /etc/gdm/Init/Default from being executed by certain versions of GDM 3: https://bugzilla.redhat.com/show_bug.cgi?id=851769 That issue is known to affect Fedora 22 and later, and it might be affecting the version of GDM shipped with Ubuntu 16.04. I've never actually tested GDM 3 on Ubuntu 16, because I can't even get it to start properly. LightDM is the only version that works on my system. Try modifying /etc/gdm3/Init/Default and add: echo test >/tmp/test to the top. Restart GDM. If /tmp/test doesn't get created, then you are likely running into the aforementioned issue, and the only known workaround is to use LightDM. On 10/5/16 2:50 AM, Wolfgang Verestek wrote: > Thanks for the reply. The link solved some issues with the nvidia driver. > But the original problem remains, I'm not able to connect to display :0. > > [VGL] Shared memory segment ID for vglconfig: 5734445 > [VGL] VirtualGL v2.5.1 64-bit (Build 20161001) > [VGL] Opening connection to 3D X server 0 > [VGL] ERROR: Could not open display 0. > > On the other hand if I start vnc and use "startx" in a terminal to start a > new X server, I can open a 3d application with 2vglrun -d :1 application". > > wolfgang@WS-Mikro:~$ startx > X.Org X Server 1.18.3 > Release Date: 2016-04-04 > X Protocol Version 11, Revision 0 > Build Operating System: Linux 3.13.0-92-generic x86_64 Ubuntu > Current Operating System: Linux WS-Mikro 4.4.0-38-generic #57-Ubuntu SMP Tue > Sep 6 15:42:33 UTC 2016 x86_64 > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic > root=UUID=0aed3666-5f62-49e1-b57c-7a64d6318dd1 ro splash quiet nomodeset > Build Date: 22 July 2016 07:50:34AM > xorg-server 2:1.18.3-1ubuntu2.3 (For technical support please see > http://www.ubuntu.com/support) > Current version of pixman: 0.33.6 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.1.log", Time: Wed Oct 5 09:24:17 2016 > (==) Using system config directory "/usr/share/X11/xorg.conf.d" > The XKEYBOARD keymap compiler (xkbcomp) reports: >> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols >> Ignoring extra symbols > Errors from xkbcomp are not fatal to the X server > > wolfgang@WS-Mikro:~$ vglrun -d :1 /opt/ovito-2.7.0-x86_64/bin/ovito > QXcbConnection: Failed to initialize XRandr > Qt: XKEYBOARD extension not present on the X server. > > So to me this seems to be more a problem of permissions and rights. For this > I found that /etc/opt/VirtualGL/vgl_xauth_key is not present. Runnning > vglgenkey results in > > wolfgang@WS-Mikro:~$ /opt/VirtualGL/bin/vglgenkey > xauth: timeout in locking authority file /etc/opt/VirtualGL/vgl_xauth_key > xauth: timeout in locking authority file /etc/opt/VirtualGL/vgl_xauth_key > chmod: cannot access '/etc/opt/VirtualGL/vgl_xauth_key': No such file or > directory > > Resp. > > wolfgang@WS-Mikro:~$ sudo /opt/VirtualGL/bin/vglgenkey > xauth: file /etc/opt/VirtualGL/vgl_xauth_key does not exist > xauth: (argv):1: couldn't query Security extension on display ":4" > xauth: file /etc/opt/VirtualGL/vgl_xauth_key does not exist > xauth: (argv):1: bad "add" command line > chmod: cannot access '/etc/opt/VirtualGL/vgl_xauth_key': No such file or > directory > > In /etc/gdm3/Init/Default there is a line with "xhost +local" but vglgenkey > is not called. So the question I'm asking myself right now is where and when > should vglgenkey be called? > > -----Ursprüngliche Nachricht----- > Von: DRC [mailto:dcomman...@users.sourceforge.net] > Gesendet: Freitag, 30. September 2016 18:46 > An: virtualgl-users@lists.sourceforge.net > Betreff: Re: [VirtualGL-Users] Ubuntu 16.04 + VNC + VirtualGL: No protocol > specified /unable to open display :0 > > I've successfully used Ubuntu 16.04 with the distribution-supplied nVidia > driver package and VirtualGL 2.5, so I know that that configuration works > properly. It seems that the root of the problem is that your 3D X server > (display :0) isn't starting, which has nothing to do with VirtualGL. I > assume that you are unable to log into the machine locally? > > My best advice would be to try re-installing the nVidia driver package and > rebooting. Also double-check that the nouveau driver isn't installed, as > that can cause conflicts with the proprietary nVidia driver. It seems like > you might be running into the same problem described here: > https://devtalk.nvidia.com/default/topic/951741/linux/locked-out-of-xwindows > -login-loop-after-driver-upgrade-ubuntu-16-04/, > in which case you should try the troubleshooting advice from that thread. > > > On 9/30/16 6:58 AM, Wolfgang Verestek wrote: >> >> >> Dear VirtualGL users, >> >> I need some help with 3D visualization. I'm using a workstation for >> visualization of some simulation data. For this we were using Ubuntu >> 14.04 + VNC and VirtualGL for 3D applications (gnome, xfce4 as Desktop > environment). >> Everything was working, but after upgrading to 16.04 I just cannot get >> VirtualGL running properly utilizing the Nvidia GPU (Titan Z). >> >> wolfgang@WS-Mikro:~$ lspci | grep VGA >> 07:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED >> Graphics Family (rev 30) >> 83:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce >> GTX TITAN Z] (rev a1) >> >> wolfgang@WS-Mikro:~$ lspci | grep NVIDIA >> 83:00.0 VGA compatible controller: NVIDIA Corporation GK110B [GeForce >> GTX TITAN Z] (rev a1) >> 83:00.1 Audio device: NVIDIA Corporation GK110 HDMI Audio (rev a1) >> 84:00.0 3D controller: NVIDIA Corporation GK110B [GeForce GTX TITAN Z] >> (rev >> a1) >> >> wolfgang@WS-Mikro:~$ vglrun +v glxgears [VGL] Shared memory segment ID >> for vglconfig: 950279 [VGL] VirtualGL v2.5 64-bit (Build 20160215) >> [VGL] Opening connection to 3D X server :0 No protocol specified [VGL] >> ERROR: Could not open display :0. >> >> >> in /etc/log/Xorg.0.log i get some error messages, but to be honest i >> have no idea how to resolve this issue... >> wolfgang@WS-Mikro:~$ tail /var/log/Xorg.0.log >> [ 251.081] (WW) Disabling Mouse0 >> [ 251.081] (WW) Disabling Keyboard0 >> [ 251.081] (EE) [drm] Failed to open DRM device for (null): -22 >> [ 251.081] (EE) [drm] Failed to open DRM device for (null): -22 >> [ 251.081] (EE) [drm] Failed to open DRM device for (null): -22 >> [ 251.082] (EE) [drm] Failed to open DRM device for (null): -22 >> [ 251.082] (EE) [drm] Failed to open DRM device for pci:0000:83:00.0: > -22 >> [ 251.082] (EE) [drm] Failed to open DRM device for pci:0000:84:00.0: > -22 >> [ 251.082] Number of created screens does not match number of detected >> devices. >> Configuration failed. >> VNC-Screen: >> wolfgang@WS-Mikro:~$ tail /var/log/Xorg.4.log >> [ 10.046] xorg-server 2:1.15.1-0ubuntu2.6 (For technical support please >> see http://www.ubuntu.com/support) >> [ 10.046] Current version of pixman: 0.30.2 >> [ 10.046] Before reporting problems, check http://wiki.x.org >> to make sure that you have the latest version. >> [ 10.046] Markers: (--) probed, (**) from config file, (==) default >> setting, >> (++) from command line, (!!) notice, (II) informational, >> (WW) warning, (EE) error, (NI) not implemented, (??) unknown. >> [ 10.046] (==) Log file: "/var/log/Xorg.4.log", Time: Mon Mar 2 > 10:46:31 >> 2015 >> [ 10.046] (==) Using config file: "/etc/X11/xorg.conf" >> [ 10.046] (==) Using system config directory > "/usr/share/X11/xorg.conf.d" >> >> >> X server is running, also e.g. xclock works on the VNC screen. >> wolfgang@WS-Mikro:~$ w >> 16:02:51 up 30 min, 2 users, load average: 2,16, 2,35, 1,67 >> USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT >> dummy_us tty7 :0 15:32 30:42 8:57 0.09s >> update-notifier >> wolfgang pts/0 10.132.2.119 15:36 5:27 7.77s 0.23s -bash >> >> wolfgang@WS-Mikro:~$ nvidia-smi >> Wed Sep 28 16:02:54 2016 >> +------------------------------------------------------+ >> | NVIDIA-SMI 361.42 Driver Version: 361.42 | >> |-------------------------------+----------------------+-------------- >> |-------------------------------+----------------------+------ >> --+ >> | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. >> ECC | >> | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute >> M. | >> |===============================+======================+============== >> |====== >> ==| >> | 0 GeForce GTX TIT... Off | 0000:83:00.0 On | >> N/A | >> | 36% 50C P8 28W / 189W | 95MiB / 6143MiB | 0% >> Default | >> +-------------------------------+----------------------+-------------- >> +-------------------------------+----------------------+------ >> --+ >> | 1 GeForce GTX TIT... Off | 0000:84:00.0 Off | >> N/A | >> | 33% 47C P8 33W / 189W | 15MiB / 6143MiB | 0% >> Default | >> +-------------------------------+----------------------+-------------- >> +-------------------------------+----------------------+------ >> --+ >> >> +--------------------------------------------------------------------- >> +------ >> --+ >> | Processes: GPU >> Memory | >> | GPU PID Type Process name Usage >> | >> |===================================================================== >> |====== >> ==| >> | 0 2968 G /usr/lib/xorg/Xorg >> 33MiB | >> | 0 3262 G /usr/bin/gnome-shell >> 43MiB | >> +--------------------------------------------------------------------- >> +------ >> --+ >> >> xorg.conf (which was working on 14.04 LTS): >> Code: >> >> Section "DRI" >> Mode 0666 >> EndSection >> >> Section "ServerLayout" >> Identifier "Layout0" >> Screen 0 "Screen0" 0 0 >> Screen 1 "Screen1" RightOf "Screen0" >> InputDevice "Keyboard0" "CoreKeyboard" >> InputDevice "Mouse0" "CorePointer" >> Option "Xinerama" "0" >> EndSection >> >> Section "Files" >> EndSection >> >> Section "InputDevice" >> >> # generated from default >> Identifier "Mouse0" >> Driver "mouse" >> Option "Protocol" "auto" >> Option "Device" "/dev/psaux" >> Option "Emulate3Buttons" "no" >> Option "ZAxisMapping" "4 5" >> EndSection >> >> Section "InputDevice" >> >> # generated from default >> Identifier "Keyboard0" >> Driver "kbd" >> EndSection >> >> Section "Monitor" >> Identifier "Monitor0" >> VendorName "Unknown" >> ModelName "BenQ G2200W" >> HorizSync 31.0 - 83.0 >> VertRefresh 55.0 - 76.0 >> Option "DPMS" >> EndSection >> >> Section "Monitor" >> Identifier "Monitor1" >> VendorName "Unknown" >> ModelName "Dell DEL 1908FPBLK" >> HorizSync 30.0 - 81.0 >> VertRefresh 56.0 - 76.0 >> EndSection >> >> Section "Device" >> Identifier "Device0" >> Driver "nvidia" >> VendorName "NVIDIA Corporation" >> BoardName "GeForce GTX TITAN Z" >> BusID "PCI:83:0:0" >> Screen 0 >> EndSection >> >> Section "Device" >> Identifier "Device1" >> Driver "nvidia" >> VendorName "NVIDIA Corporation" >> BoardName "GeForce GTX TITAN Z" >> BusID "PCI:84:0:0" >> Screen 1 >> EndSection >> >> Section "Screen" >> Identifier "Screen0" >> Device "Device0" >> Monitor "Monitor0" >> DefaultDepth 24 >> Option "Stereo" "0" >> Option "nvidiaXineramaInfoOrder" "DFP-0" >> Option "metamodes" "DVI-I-1: nvidia-auto-select +0+0" >> Option "SLI" "Off" >> Option "MultiGPU" "On" >> Option "BaseMosaic" "off" >> Option "AllowGLXWithComposite" "true" >> SubSection "Display" >> Depth 24 >> EndSubSection >> EndSection >> >> Section "Screen" >> Identifier "Screen1" >> Device "Device1" >> Monitor "Monitor1" >> DefaultDepth 24 >> Option "Stereo" "0" >> Option "metamodes" "DVI-D-0: nvidia-auto-select +0+0" >> Option "SLI" "Off" >> Option "MultiGPU" "On" >> Option "BaseMosaic" "off" >> Option "AllowGLXWithComposite" "true" >> SubSection "Display" >> Depth 24 >> EndSubSection >> EndSection >> >> I hope somebody can give me a hint how to resolve that issue. If some >> additional info is needed let me know. >> >> >> Best regards >> Wolfgang > > ---------------------------------------------------------------------------- > -- > _______________________________________________ > VirtualGL-Users mailing list > VirtualGL-Users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtualgl-users > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > VirtualGL-Users mailing list > VirtualGL-Users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtualgl-users > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
