VirtualGL 2.4 is quite old. Before I can provide support for these
issues, you will need to verify whether they still exist in the latest
version. Please download and install VirtualGL 2.5.2. In general, I do
not recommend using O/S-supplied builds of VirtualGL. They are
typically outdated and sometimes are not implemented correctly. For
instance, the Fedora implementation places the faker libraries under
/usr/lib64/VirtualGL, which means that their build cannot be used to run
setuid root applications
(https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/index.html#hd0012).
Other distributions, such as Arch, have historically bundled VirtualGL
incorrectly, leading to problems with applications that use dlopen() to
load libGL. Furthermore, new releases of VirtualGL almost always
contain application compatibility fixes. That's why, if you are
experiencing an issue with a particular application, the first thing you
should always try is upgrading to the latest official build of VirtualGL.
In short, if you are using an O/S-supplied build of VirtualGL, then you
should seek support from the O/S distributor. I can only support the
builds that I provide.
DRC
On 11/16/17 9:41 AM, Angel de Vicente wrote:
> But I have some other bigger problems now :-(
>
> I have three visualization packages that we would like to use: VisIt,
> Mayavi2 and Paraview, and I'm trying them both with vglconnect and with
> TurboVNC. And the situations for each package is as follows:
>
> + VisIt (version 2.12.3)
> -------
> This behaves apparently OK. Either with (vglconnect / vglrun) or with
> (TurboVNC / vglrun) I can start VisIt (2.12.3), can resize windows, open
> some files, visualize some data, etc. The only noticeable difference is
> that when I start it as (vglconnect / vglrun) I have to specify the name
> of the client machine, and I get those innocent swrast messages (which I
> don't get when I'm running inside TurboVNC). This is the output when
> running in (vglconnect / vglrun):
>
> ,----
> | [angelv@deim ~]$ vglrun +v -cl com visit
> | [VGL] NOTICE: Added /usr/lib64/VirtualGL to LD_LIBRARY_PATH
> | Running: gui2.12.3
> | [VGL] Shared memory segment ID for vglconfig: 14909450
> | [VGL] VirtualGL v2.4 64-bit (Build 20170210)
> | [VGL] Opening connection to 3D X server :0
> | Unable to load library icui18n "Cannot load library icui18n: (icui18n:
> | cannot open shared object file: No such file or directory)"
> | QGtkStyle was unable to detect the current GTK+ theme.
> | Running: viewer2.12.3 -geometry 1063x1063+857+17 -borders 29,3,3,3
> | -shift 22,29 -preshift -19,0 -defer -host 127.0.0.1 -port 5600
> | [VGL] Shared memory segment ID for vglconfig: 14942221
> | [VGL] VirtualGL v2.4 64-bit (Build 20170210)
> | [VGL] Opening connection to 3D X server :0
> | Running: mdserver2.12.3 -host 127.0.0.1 -port 5601
> | [VGL] NOTICE: Replacing dlopen("/usr/lib64/libdl.so.2") with
> | dlopen("libdlfaker.so")
> | libGL error: No matching fbConfigs or visuals found
> | libGL error: failed to load driver: swrast
> | [VGL] Using Pbuffers for rendering
> | [VGL] Using 1 / 20 CPU's for compression
> | [VGL] Using pixel buffer objects for readback (BGRA --> BGRA)
> | [VGL] Client version: 2.1
> | Running: engine_ser2.12.3 -host 127.0.0.1 -port 5600
> `----
>
>
> + Paraview (version 5.4.0)
>
> If I run it with (vglconnect / vglrun) I can at least load and show a
> basic image, but I cannot resize the window, as can be seen in the image:
> http://picpaste.com/paraview-vglconnect-1Jpzk5sZ.png
>
> If I try to run it inside TurboVNC, I get nasty GL errors about failing
> to create context, as can be seen in the image:
> http://picpaste.com/paraview-turbovnc-G6pA04dg.png
>
>
> + Mayavi (version 4.5.0)
>
> This one complains about GLEW and core dumps...
>
> If running (vglconnect / vglrun)
> ,----
> | [angelv@deim ~]$ vglrun +v -cl com mayavi2
> | [VGL] NOTICE: Added /usr/lib64/VirtualGL to LD_LIBRARY_PATH
> | [VGL] Shared memory segment ID for vglconfig: 15695882
> | [VGL] VirtualGL v2.4 64-bit (Build 20170210)
> | [VGL] Opening connection to 3D X server :0
> | Bus::open: Can not get ibus-daemon's address.
> | IBusInputContext::createInputContext: no connection to ibus-daemon
> | libGL error: No matching fbConfigs or visuals found
> | libGL error: failed to load driver: swrast
> | [VGL] Selecting structure notify events in window 0x06400025
> | [VGL] Using Pbuffers for rendering
> | ERROR: In
> |
> /builddir/build/BUILD/VTK-7.1.1/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> | line 628
> | vtkXOpenGLRenderWindow (0x5636f7557970): GLEW could not be initialized.
> |
> | Segmentation fault (core dumped)
> | [angelv@deim ~]$
> `----
>
> If running (TurboVNC / vglrun)
>
> ,----
> | [angelv@deim ~]$ vglrun +v mayavi2
> | [VGL] NOTICE: Added /usr/lib64/VirtualGL to LD_LIBRARY_PATH
> | [VGL] Shared memory segment ID for vglconfig: 15859722
> | [VGL] VirtualGL v2.4 64-bit (Build 20170210)
> | [VGL] Opening connection to 3D X server :0
> | [VGL] Selecting structure notify events in window 0x02a00027
> | [VGL] Using Pbuffers for rendering
> | ERROR: In
> |
> /builddir/build/BUILD/VTK-7.1.1/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> | line 628
> | vtkXOpenGLRenderWindow (0x557f2571f680): GLEW could not be initialized.
> |
> | Segmentation fault (core dumped)
> | [angelv@deim ~]$
> `----
>
>
> Any ideas?
>
> Many thanks,
> AdV
--
You received this message because you are subscribed to the Google Groups
"VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/virtualgl-users/067780e0-ea9c-761f-4289-7bee2fe8f30e%40virtualgl.org.
For more options, visit https://groups.google.com/d/optout.
