# Paraview won't start, related to ADIOS2

**URL:** https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646
**Category:** Uncategorized
**Created:** [November 4, 2023, 10:59am UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646 "2023-11-04T10:59:26Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![raboynics](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@raboynics](https://fenicsproject.discourse.group/u/raboynics)
#### Post date: [November 4, 2023, 10:59am UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/1 "2023-11-04T10:59:26Z")

</div>

I use Paraview on Arch Linux. It seems like the package adios2 is a requirement for Paraview, and since I also want to switch from XDMF to ADIOS2, I’d like to stick to ADIOS2. However Paraview won’t run.

Starting it with a terminal yields: `/opt/paraview/bin/paraview: symbol lookup error: /opt/paraview/lib/libvtkfides.so.1: undefined symbol: _ZN6adios25ADIOSC1Eb `  
Google returns 0 answer. While it’s a Paraview error (too lazy to create an account to report it there), I wonder how you guys managed not to get this error. (Especially those with Arch Linux).

---

<div class="post-metadata">

### Author: ![Ekrem\_Ekici](https://avatars.discourse-cdn.com/v4/letter/e/977dab/32.png) [@Ekrem\_Ekici](https://fenicsproject.discourse.group/u/Ekrem_Ekici)
#### Post date: [November 4, 2023, 10:06pm UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/2 "2023-11-04T22:06:06Z")

</div>

I have the same problem. V0.7.1 did not fixed this problem for me.

---

<div class="post-metadata">

### Author: ![nate](https://yyz2.discourse-cdn.com/free1/user_avatar/fenicsproject.discourse.group/nate/32/17_2.png) [@nate](https://fenicsproject.discourse.group/u/nate)
#### Post date: [November 4, 2023, 10:39pm UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/3 "2023-11-04T22:39:52Z")

</div>

I’ve had a similar issue in the past where paraview was attempting to link against my system’s build of adios2 rather than its own internal binaries. If you call `ldd /opt/paraview/lib/libvtkfides.so.1` or `ldd` on your paraview executable you might get some insight.

---

<div class="post-metadata">

### Author: ![raboynics](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@raboynics](https://fenicsproject.discourse.group/u/raboynics)
#### Post date: [November 5, 2023, 8:17am UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/4 "2023-11-05T08:17:03Z")

</div>

Apparently, it’s an ADIOS2 problem. As a quick fix I downgraded the adios2 package and Paraview runs fine. The bug has been reported a few days ago I think.

---

<div class="post-metadata">

### Author: ![Ekrem\_Ekici](https://avatars.discourse-cdn.com/v4/letter/e/977dab/32.png) [@Ekrem\_Ekici](https://fenicsproject.discourse.group/u/Ekrem_Ekici)
#### Post date: [November 8, 2023, 12:21pm UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/5 "2023-11-08T12:21:10Z")

</div>

Did you recompile dolfinx after downgrading adios2? @raboynics

---

<div class="post-metadata">

### Author: ![raboynics](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@raboynics](https://fenicsproject.discourse.group/u/raboynics)
#### Post date: [November 8, 2023, 7:16pm UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/6 "2023-11-08T19:16:39Z")

</div>

No. I use docker, so no compilation. I didn’t update anything.

---

<div class="post-metadata">

### Author: ![carlosal1015](https://yyz2.discourse-cdn.com/free1/user_avatar/fenicsproject.discourse.group/carlosal1015/32/4193_2.png) [@carlosal1015](https://fenicsproject.discourse.group/u/carlosal1015)
#### Post date: [February 8, 2024, 5:49pm UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/7 "2024-02-08T17:49:03Z")

</div>

Hi @raboynics I noticed the same error but when I opened a XDMF file. I could report the error (I have my Arch Linux GitLab credentials set up). My solution was [export to VTK file]([dolfinx-demo/poisson.py at main · cpp-review-dune/dolfinx-demo · GitHub](https://github.com/cpp-review-dune/dolfinx-demo/blob/main/poisson.py#L46-) L48).

Could you provide an example for adios2 file in order to prepare an issue [here](https://gitlab.archlinux.org/archlinux/packaging/packages/paraview/-/issues).

Is related with this issue? [Opening ADIOS2 bp files leads to core dump (#3) · Issues · Arch Linux / Packaging / Packages / paraview · GitLab](https://gitlab.archlinux.org/archlinux/packaging/packages/paraview/-/issues/3)

---

<div class="post-metadata">

### Author: ![raboynics](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@raboynics](https://fenicsproject.discourse.group/u/raboynics)
#### Post date: [February 8, 2024, 8:25pm UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/8 "2024-02-08T20:25:29Z")

</div>

I don’t have the time right now nor in the next weeks to try these things. I resorted to use Paraview from the website itself rather than the Arch Linux package (whixh was still broken a few days ago when opening solution files, but not in xdmf format).

---

<div class="post-metadata">

### Author: ![dparsons](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@dparsons](https://fenicsproject.discourse.group/u/dparsons)
#### Post date: [February 9, 2024, 9:49am UTC](https://fenicsproject.discourse.group/t/paraview-wont-start-related-to-adios2/12646/9 "2024-02-09T09:49:10Z")

</div>

For the debian build of paraview 5.11.2, I had to apply a dozen patches from HEAD so it would work with adios2 2.9.2. It seems to be running smoothly, with dolfinx 0.7.3.
