# ParaView in Headless Mode with OSMesa, EGL, and libX11

**URL:** https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109
**Category:** ParaView Support
**Created:** [February 5, 2025, 10:38am UTC](https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109 "2025-02-05T10:38:34Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![s1291](https://discourse.paraview.org/user_avatar/discourse.paraview.org/s1291/32/15950_2.png) [@s1291](https://discourse.paraview.org/u/s1291)
#### Post date: [February 5, 2025, 10:38am UTC](https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109/1 "2025-02-05T10:38:34Z")

</div>

Is it possible to compile a single version of ParaView that supports OSMesa, EGL, and libX11 at the **same time**?

I ask because I recall seeing a version of ParaView on an HPC cluster that appeared to be compiled with all three libraries **simultaneously**. I had assumed these libraries were mutually exclusive.

Can someone explain how this is possible?

Thank you.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [February 5, 2025, 1:12pm UTC](https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109/2 "2025-02-05T13:12:54Z")

</div>

This is currently not possible, but will be possible if a near future as thie feature was added in VTK a few months ago.

FYI @jaswantp

---

<div class="post-metadata">

### Author: ![jaswantp](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jaswantp/32/11456_2.png) [@jaswantp](https://discourse.paraview.org/u/jaswantp)
#### Post date: [February 5, 2025, 1:16pm UTC](https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109/3 "2025-02-05T13:16:30Z")

</div>

Yes, you can use any commit of paraview starting from [e6e3fe3ce](https://gitlab.kitware.com/paraview/paraview/-/commit/e6e3fe3ce4707c58bcc8a8c7ac3b57fa9942c4e3) and use the default cmake settings.

Btw, that commit is not yet part of a release. It might be included in the upcoming release.

---

<div class="post-metadata">

### Author: ![s1291](https://discourse.paraview.org/user_avatar/discourse.paraview.org/s1291/32/15950_2.png) [@s1291](https://discourse.paraview.org/u/s1291)
#### Post date: [February 5, 2025, 1:17pm UTC](https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109/4 "2025-02-05T13:17:06Z")

</div>

But how do you explain this output:

```auto
❯ pvserver --version
paraview version 5.11.0
user@cluster1: ~
❯ ldd $(which pvserver) | grep OSMesa
        libOSMesa.so.8 => /cvmfs/soft.computeuniversity/gentoo/2020/usr/lib64/libOSMesa.so.8 (0x00007f84bf30e000)
user@cluster1: ~
❯ ldd $(which pvserver) | grep EGL
        libEGL.so.1 => /cvmfs/soft.computeuniversity/gentoo/2020/usr/lib64/libEGL.so.1 (0x00007fea7bda4000)
user@cluster1: ~
❯ ldd $(which pvserver) | grep X11
        libX11.so.6 => /cvmfs/soft.computeuniversity/gentoo/2020/usr/lib64/libX11.so.6 (0x00007f359f54b000)
user@cluster1: ~

```

---

<div class="post-metadata">

### Author: ![jaswantp](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jaswantp/32/11456_2.png) [@jaswantp](https://discourse.paraview.org/u/jaswantp)
#### Post date: [February 5, 2025, 1:19pm UTC](https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109/5 "2025-02-05T13:19:51Z")

</div>

> But how do you explain this output:

they could have simply patched ParaView to allow coexisting context providers.

---

<div class="post-metadata">

### Author: ![s1291](https://discourse.paraview.org/user_avatar/discourse.paraview.org/s1291/32/15950_2.png) [@s1291](https://discourse.paraview.org/u/s1291)
#### Post date: [February 5, 2025, 1:26pm UTC](https://discourse.paraview.org/t/paraview-in-headless-mode-with-osmesa-egl-and-libx11/16109/6 "2025-02-05T13:26:13Z")

</div>

Is there a way to find if this version is patched or not?
