[willzyba]

Any help with this would be greatly appreciated.

When we try to load a saved state within Paraview it crashes only when we are remotely connect to the workstation using XRDP and only when we ask Paraview to load a saved state. Otherwise is behaves perfectly.

Background of the system:
- The workstation is running Ubuntu 14.04.
- We use the xubuntu desktop, hopefully with all 3d features off.
- The workstation has NVidea Quadro K4000.
- We are accessing a workstation using XRDP, which we recompiled XRDP from source using the X11RDP-o-Matic.git. (Incase anyone is wondering, this gives us proper colours, mouse wheel and copy-n-paste to the hoste system).
- We're using Paraview 4.2.0 (though we get the same problem with 4.1.0 on an parallel near ideantical machine)
- Paraview in this instance was compiled from source with the follow ccmake options:

 	BUILD_DOCUMENTATION              OFF                                          
 	BUILD_EXAMPLES                   OFF                                          
 	BUILD_SHARED_LIBS                ON                                           
 	BUILD_TESTING                    OFF                                          
 	CMAKE_BUILD_TYPE                 Release                                      
 	CMAKE_INSTALL_PREFIX             /opt/ThirdParty-2.3.x/platforms/linux64Gcc/Pa
 	GMVReader_GMVREAD_LIB_DIR        /opt/ThirdParty-2.3.x/ParaView-v4.2.0-source/
 	GMVReader_SKIP_DATARANGE_CALCU   OFF                                          
 	MPI_C_INCLUDE_PATH               /opt/ThirdParty-2.3.x/platforms/linux64Gcc/op
 	MPI_C_LIBRARIES                  /opt/ThirdParty-2.3.x/platforms/linux64Gcc/op
 	PARAVIEW_BUILD_QT_GUI            ON                                           
 	PARAVIEW_ENABLE_CATALYST         ON                                           
 	PARAVIEW_ENABLE_FFMPEG           OFF                                          
 	PARAVIEW_ENABLE_PYTHON           ON                                           
 	PARAVIEW_INSTALL_DEVELOPMENT_F   ON                                           
 	PARAVIEW_USE_MPI                 ON                                           
 	PARAVIEW_USE_PISTON              OFF
	PARAVIEW_USE_UNIFIED_BINDINGS    OFF                                          
	PARAVIEW_USE_VISITBRIDGE         OFF                                          
 	SURFACELIC_PLUGIN_TESTING        ON                                           
 	VTK_RENDERING_BACKEND            OpenGL                                       
 	VTK_SMP_IMPLEMENTATION_TYPE      Sequential                                   
 	VTK_USE_LARGE_DATA               OFF                                          
 	XDMF_USE_BZIP2                   OFF                                          
 	XDMF_USE_GZIP                    OFF

I appreciate that for most work we should be using the ParaView client/server connection and running ParaView locally on the users machines - which we do. But there are many situations when its advantageous, not to say faster, if we're able to run paraview directly to the underlying workstation.

I'm basically fishing blind. These are some of the links we've looked at:
- 137941-xlib-extension-xinputextension-missing-display.html
- Disabling 3D effects

Errors:

A lot of these:

  X Error: GLXBadContextTag 159
  Extension:    148 (Uknown extension)
  Minor opcode: 115 (Unknown request)
  Resource id:  0x1

Some of these:

Generic Warning: In /opt/ThirdParty-2.3.x/ParaView-v4.2.0-source/VTK/Rendering/OpenGL/vtkOpenGLDisplayListPainter.cxx, line 52
failed after ReleaseAllLists 16 OpenGL errors detected
  0 : (9699443) Unknown error
  1 : (9699443) Unknown error
  2 : (9699443) Unknown error
  3 : (9699443) Unknown error
  4 : (9699443) Unknown error
  5 : (9699443) Unknown error
  6 : (9699443) Unknown error
  7 : (9699443) Unknown error
  8 : (9699443) Unknown error
  9 : (9699443) Unknown error
  10 : (9699443) Unknown error
  11 : (9699443) Unknown error
  12 : (9699443) Unknown error
  13 : (9699443) Unknown error
  14 : (9699443) Unknown error
  15 : (9699443) Unknown error

Finally:

X Error: GLXBadContextTag 159
  Extension:    148 (Uknown extension)
  Minor opcode: 145 (Unknown request)
  Resource id:  0x1
[xcb] Too much data requested from _XRead
[xcb] This is most likely caused by a broken X extension library
[xcb] Aborting, sorry about that.
paraview: ../../src/xcb_io.c:736: _XRead: Assertion `!xcb_xlib_too_much_data_requested' failed.
Aborted (core dumped)

Fully list of errors attached