# issue with vtkOpenGLRenderWindow on linux with vtk=9.1

**URL:** https://discourse.vtk.org/t/issue-with-vtkopenglrenderwindow-on-linux-with-vtk-9-1/8576
**Category:** Support
**Created:** [May 24, 2022, 3:18pm UTC](https://discourse.vtk.org/t/issue-with-vtkopenglrenderwindow-on-linux-with-vtk-9-1/8576 "2022-05-24T15:18:23Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![dgobbi](https://discourse.vtk.org/user_avatar/discourse.vtk.org/dgobbi/32/18_2.png) [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [June 8, 2022, 2:40pm UTC](https://discourse.vtk.org/t/issue-with-vtkopenglrenderwindow-on-linux-with-vtk-9-1/8576/5 "2022-06-08T14:40:45Z")

</div>

OpenGL 4.6 is definitely sufficient for VTK 9.1. To eliminate Qt as a possible source of the segfault, can you try a non-Qt VTK example like the [cylinder example](https://kitware.github.io/vtk-examples/site/Python/GeometricObjects/Cylinder/)?

You can also call `renderWindow.ReportCapabilities()` after the first Render to get more information about the VTK\<-\>OpenGL connection (assuming that the Render() doesn’t cause a segfault).

```python
    # Render and interact
    renderWindow.Render()
    print(renderWindow.ReportCapabilities())
    # The Start() is only for non-Qt apps
    renderWindowInteractor.Start()

```

---

_[View the full topic](https://discourse.vtk.org/t/issue-with-vtkopenglrenderwindow-on-linux-with-vtk-9-1/8576)._