OK, that is probably a legitimate bug, then. How does one obtain mayavi2? The supposed link to the application home page is dead: http://code.enthought.com/projects/mayavi/
On 11/16/17 6:31 PM, Angel de Vicente wrote: > Hello, > > El jueves, 16 de noviembre de 2017, 17:21:06 (UTC), DRC escribió: > > 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. > > > OK, thanks for the advice. I downloaded the latest RPM version, removed > the old 2.4 from the server machines and installed the new 2.5.2. > VisIt still seems OK, Paraview now doesn't give me any trouble with > window resisizing, but Mayavi2 is still giving me the same error: > > (to avoid possible issues with the ArchLinux 2.5.2 VirtualGL version, > which I didn't compile myself, I just run the test inside TurboVNC) > > [angelv@deim ~]$ vglrun +v mayavi2 > [VGL] Shared memory segment ID for vglconfig: 22118410 > [VGL] VirtualGL v2.5.2 64-bit (Build 20170302) > [VGL] Opening connection to 3D X server :0 > [VGL] Selecting structure notify events in window 0x02600027 > [VGL] Using Pbuffers for rendering > ERROR: In > /builddir/build/BUILD/VTK-7.1.1/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 628 > vtkXOpenGLRenderWindow (0x564e98fe8670): GLEW could not be initialized. > > Segmentation fault (core dumped) > [angelv@deim ~]$ > > > 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/f0ddeed2-3fbf-3268-bc24-17224526a16e%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
