[Paraview] [Non-DoD Source] Re: 5.1.2/OpenGL2 issue

[Utkarsh Ayachit]

No, that's not it. Hopefully someone with more knowledge on this than
me can chime in at some point. I'm told that VirtualGL < 2.3.1 did not
forward the glXCreateContextARB calls we need for creating OpenGL 3.2
context needed by ParaView (OpenGL2 backend).

To update my know how about it in the mean time, I read up a bit on
TightVNC and VGL [1,2]. So, is your setup intended to use VirtualGL?
If so, shouldn't you be running `vglrun paraview`? I believe that's
the [VGL] warning messages are all about, aren't they?

Utkarsh

[1] http://www.virtualgl.org/vgldoc/2_1_1/#hd009
[2] https://hpc.nrel.gov/users/software/visualization-analytics/virtualgl-turbovnc

On Wed, Aug 24, 2016 at 9:36 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Yes - this is an OpenGL2 build.
>
> Is this the information on TurboVNC that you’re looking for?
>
> server glx vendor string: VirtualGL
> server glx version string: 1.4
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Wednesday, August 24, 2016 at 8:57 AM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: ParaView <paraview at paraview.org>
> Subject: [Non-DoD Source] Re: [Paraview] 5.1.2/OpenGL2 issue
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to a
> Web browser.
>
>
>
>
> ----
>
> Rick,
>
> I am assuming with is with VTK_RENDERING_BACKEND set to OpenGL2.
>
> Do you know what VirtualGL version is being used?
>
> On Tue, Aug 23, 2016 at 2:56 PM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> We are trying to build/run ParaView 5.1.2 on a particular HPC system with
>> graphics nodes via TurboVNC.     ParaView 5.0.1 build/runs fine in this
>> configuration.    ParaView 5.1.2 compiles fine (using identical build
>> configuration used to build 5.0.1) - however the GUI fails at execution.
>> I’m not sure how to debug it any further.     It *appears* that 5.1.2 is
>> maybe doing some additional environment querying that might be causing
>>this
>> failure?
>>
>>
>> When I try to run 5.1.2, I get this error:
>>
>> g01 > paraview
>> [VGL] WARNING: The OpenGL rendering context obtained on X display
>> [VGL]    :0.0 is indirect, which may cause performance to suffer.
>> [VGL]    If :0.0 is a local X display, then the framebuffer device
>> [VGL]    permissions may be set incorrectly.
>> Segmentation fault
>>
>>
>> The particular message about indirect rendering – if I run glxinfo,
>>direct
>> rendering is set to YES.
>>
>> g01 > glxinfo
>> name of display: :5.0
>> display: :5  screen: 0
>> direct rendering: Yes
>> server glx vendor string: VirtualGL
>> server glx version string: 1.4
>> [deleted stuff]
>> OpenGL vendor string: NVIDIA Corporation
>> OpenGL renderer string: Tesla K40m/PCIe/SSE2
>> OpenGL core profile version string: 4.3.0 NVIDIA 340.93
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>> _______________________________________________
>> Powered by Caution-www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> Caution-http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> Caution-http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at:
>>Caution-http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> Caution-http://public.kitware.com/mailman/listinfo/paraview
>>