# \--mesa seems broken in 5.6.1

**URL:** https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357
**Category:** Development
**Created:** [August 4, 2019, 5:56pm UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357 "2019-08-04T17:56:40Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![ftoth](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/76d3ee/32.png) [@ftoth](https://discourse.paraview.org/u/ftoth)
#### Post date: [August 4, 2019, 5:56pm UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357/1 "2019-08-04T17:56:41Z")

</div>

Hi,

After upgrading to 5.6.1 we get crashes with

> $ paraview --mesa-llvm  
> : CommandLine Error: Option ‘help-list’ registered more than once!  
> LLVM ERROR: inconsistency in registered CommandLine options

We’re using mesa in an x2go sessions or on virtual machines. Above option used to work in 5.6.0.

Occurs using the official ParaView download [https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.6&type=binary&os=Linux&downloadFile=ParaView-5.6.1-MPI-Linux-64bit.tar.gz](https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.6&type=binary&os=Linux&downloadFile=ParaView-5.6.1-MPI-Linux-64bit.tar.gz)

Any idea what the problem could be?

Regards,  
Florian

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 5, 2019, 12:14pm UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357/2 "2019-08-05T12:14:14Z")

</div>

I assume you mean “5.6.1” here. That option seems to be related to a conflicting Mesa/LLVM being found. @utkarsh.ayachit @chuckatkins @Dave_DeMarle Where did we see this before?

---

<div class="post-metadata">

### Author: ![Dave\_DeMarle](https://discourse.paraview.org/user_avatar/discourse.paraview.org/dave_demarle/32/27_2.png) [@Dave\_DeMarle](https://discourse.paraview.org/u/Dave_DeMarle)
#### Post date: [August 5, 2019, 12:31pm UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357/3 "2019-08-05T12:31:21Z")

</div>

This shows up at TACC on stampede2. There, we detect both system OpenGL and our own GL, which happen to have incompatible llvm versions, and the cmake flag to prefer our own was not sufficient to avoid the problem. My temporary workaround there was a hack to force really disabling system OpenGL.

In a few days I should have time to come up with a real fix. Florian it would be helpful if you can tell us if your system configuration is similar.

---

<div class="post-metadata">

### Author: ![ftoth](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/76d3ee/32.png) [@ftoth](https://discourse.paraview.org/u/ftoth)
#### Post date: [August 5, 2019, 1:49pm UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357/4 "2019-08-05T13:49:35Z")

</div>

the server is a centos7 (3.10.0-957.1.3.el7.x86\_64) machine accessed via x2go (version 4.1.0.3) . In the x2go-session I have

> $ glxinfo | grep “OpenGL”  
> OpenGL vendor string: VMware, Inc.  
> OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)  
> OpenGL version string: 2.1 Mesa 18.0.5  
> OpenGL shading language version string: 1.30

Since I’m not familiar with TACC on stampede2, I can’t tell if that’s similar. But I’ll be happy to provide more information if you tell me what you want to know 🙂

---

<div class="post-metadata">

### Author: ![ftoth](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/76d3ee/32.png) [@ftoth](https://discourse.paraview.org/u/ftoth)
#### Post date: [September 23, 2019, 9:55am UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357/5 "2019-09-23T09:55:11Z")

</div>

Hi,

I’ve upgraded to 5.6.2 gut get a new problem there: running PV with any --mesa option I get

> /mypath/ParaView-5.6.2-MPI-Linux-64bit/bin/paraview --mesa  
> /mypath/ParaView-5.6.2-MPI-Linux-64bit/lib/paraview: /mypath/ParaView-5.6.2-MPI-Linux-64bit/lib/mesa/libz.so.1: version `ZLIB\_1.2.9’ not found (required by /mypath/ParaView-5.6.2-MPI-Linux-64bit/lib/libpng16.so.16)

My system Zlib on Centos7 is 1.2.7, however I’m using again the pre-build binaries form the official homepage, so system libs should be irrelevant in this case I guess.

Any suggestions on how to get the GUI running without OpenGL (i.e. in VMs or via x2go)?

---

<div class="post-metadata">

### Author: ![n0xn4me](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/n/b487fb/32.png) [@n0xn4me](https://discourse.paraview.org/u/n0xn4me)
#### Post date: [February 19, 2021, 8:35pm UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357/6 "2021-02-19T20:35:31Z")

</div>

Did you ever find a resolution for this? I am running into the same issue.

Thanks.

---

<div class="post-metadata">

### Author: ![ftoth](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/76d3ee/32.png) [@ftoth](https://discourse.paraview.org/u/ftoth)
#### Post date: [February 20, 2021, 1:21pm UTC](https://discourse.paraview.org/t/mesa-seems-broken-in-5-6-1/2357/7 "2021-02-20T13:21:33Z")

</div>

as far as I’m aware it is solved in paraview \>= 5.7
