# pvpython offscreen rendering segfault

**URL:** https://discourse.paraview.org/t/pvpython-offscreen-rendering-segfault/246
**Category:** ParaView Support
**Created:** [June 28, 2018, 9:46am UTC](https://discourse.paraview.org/t/pvpython-offscreen-rendering-segfault/246 "2018-06-28T09:46:36Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Lukas](https://discourse.paraview.org/user_avatar/discourse.paraview.org/lukas/32/114_2.png) [@Lukas](https://discourse.paraview.org/u/Lukas)
#### Post date: [June 28, 2018, 3:56pm UTC](https://discourse.paraview.org/t/pvpython-offscreen-rendering-segfault/246/3 "2018-06-28T15:56:37Z")

</div>

Hey Scott,

Many thanks for your quick reply!  
I interpreted the documentation differently:

> If `VTK_OPENGL_HAS_EGL` or `VTK_OPENGL_HAS_OSMESA` is ON, the build supports headless rendering, otherwise VTK\_USE\_X must be ON and the build does not support headless, but can still support offscreen rendering.

If `VTK_OPENGL_HAS_EGL=ON` or `VTK_OPENGL_HAS_OSMESA=ON` → headless support  
otherwise (`VTK_OPENGL_HAS_EGL=OFF` and `VTK_OPENGL_HAS_OSMESA=OFF`) → no headless support and `VTK_USE_X` must be turned on.

However, it does not exclude the case where `VTK_OPENGL_HAS_OSMESA=ON` and `VTK_USE_X=ON`.

Further down it is mentioned that:

> it’s possible to build ParaView with onscreen and headless support simultaneously

Is this a fault in the documentation?

Thanks again,  
Lukas

---

_[View the full topic](https://discourse.paraview.org/t/pvpython-offscreen-rendering-segfault/246)._
