# Inconsistency detected by ld.so

**URL:** https://discourse.paraview.org/t/inconsistency-detected-by-ld-so/3778
**Category:** ParaView Support
**Created:** [March 9, 2020, 5:34pm UTC](https://discourse.paraview.org/t/inconsistency-detected-by-ld-so/3778 "2020-03-09T17:34:36Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Senui](https://discourse.paraview.org/user_avatar/discourse.paraview.org/senui/32/1403_2.png) [@Senui](https://discourse.paraview.org/u/Senui)
#### Post date: [March 9, 2020, 5:34pm UTC](https://discourse.paraview.org/t/inconsistency-detected-by-ld-so/3778/1 "2020-03-09T17:34:36Z")

</div>

Hello,

Using the official ParaView binaries `ParaView-5.8.0-MPI-Linux-Python3.7-64bit` on Ubuntu 16.04, I get an error when doing

```auto
pvpython foo.py

```

where foo.py only contains the line `from paraview.simple import *`

```auto
Inconsistency detected by ld.so: dl-close.c: 811: _dl_close: Assertion `map->l_init_called' failed!

```

My colleague with the same OS can reproduce on his machine.

Any ideas on what might cause this?

**Edit**  
When I add to `foo.py` the following commands, there is no more error:

```auto
Show(Cone())

```

Using strace we found that the following libraries are loaded additionally when we `Show()` something:

```auto
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
/usr/lib/x86_64-linux-gnu/libdrm_intel.so.1
/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
/usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1

```

The strace command:

```auto
strace -e open pvpython foo.py |& grep "\.so" | grep -v "= -1" | grep -o '".*"' | sed 's/"//g' | sort | uniq

```

So apparantly loading these libraries fixes the issues at hand. However, it is still not expected behavior I would say…

Cheers,  
Ahmad

---

<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: [March 10, 2020, 4:44am UTC](https://discourse.paraview.org/t/inconsistency-detected-by-ld-so/3778/2 "2020-03-10T04:44:31Z")

</div>

Unable to reproduce here. ArchLinux (Intel Chipset and NVIDIA card) and Ubuntu 18.04 (NVIDIA card).

---

<div class="post-metadata">

### Author: ![Senui](https://discourse.paraview.org/user_avatar/discourse.paraview.org/senui/32/1403_2.png) [@Senui](https://discourse.paraview.org/u/Senui)
#### Post date: [March 10, 2020, 10:50am UTC](https://discourse.paraview.org/t/inconsistency-detected-by-ld-so/3778/3 "2020-03-10T10:50:46Z")

</div>

I remember trying this on 18.04 and not having this issue either. I think it might be a Ubuntu 16.04-specific issue. Also I have no dedicated graphics card and an Intel CPU (with integrated GPU).

---

<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: [March 11, 2020, 2:58am UTC](https://discourse.paraview.org/t/inconsistency-detected-by-ld-so/3778/4 "2020-03-11T02:58:25Z")

</div>

With 16.04 EOL in roughly a year, I would not expect this to be fixed or investigated.

---

<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: [March 21, 2020, 2:14am UTC](https://discourse.paraview.org/t/inconsistency-detected-by-ld-so/3778/5 "2020-03-21T02:14:08Z")

</div>

Yeah, I think our CentOS 7 builder is “newer” than 16.04 and therefore it’s not a supported platform for the official binaries. Building your own ParaView binaries should be possible though.