I wondered if anyone in this community has experienced the issue of getting OpenGL to work on two computers separately but not when connected remotely with VPN and SSH.
I have a local installation of ParaView 5.7.0 at the office which opens up the windows normally. Likewise, with another installation at home. Troubles occurs as I connect from home to the office computer via VPN and SSH (ssh -YC etc etc). When I launch the remote PV from a ssh’ed terminal, PV aborts with the error
I isolated that ParaView cannot create a window with OpenGL. Indeed, glxinfo on the ssh’ed terminal returns the “X_GLXCreateNewContext” error
name of display: localhost:10.0
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 37
Current serial number in output stream: 38
Note that glxgears does very well in my home computer. Also, at home, glxinfo goes farther than that and finds all it needs:
name of display: :0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
Also, at home I manage to open without problems other programs natively installed in the remote network.
There is a difference between drivers at home and at the office, but this seems normal to me.
So, alas, something is lacking either in my own installation of ParaView at the office or in the way I launch it from home.
Is there a way to inform ParaView, hence OpenGL, that it has to adjust (something) when I call it from a ssh’ed terminal?
That is, from home rather from the office?
Thanks for the clarification. It helps banging one’s head on the right wall.
Would you please direct me to some entry points concerning vncviewer and suchlike applied to PV? I am not familiar with the concept. If these toolkits are meant to support PV client/server connections only, any additional information is unnecessary, however.