# Failed to use on Fedora 30
**URL:** https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484
**Category:** ParaView Support
**Created:** [August 29, 2019, 11:28am UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484 "2019-08-29T11:28:15Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@amivaleo](https://discourse.paraview.org/u/amivaleo)
#### Post date: [August 29, 2019, 11:28am UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/1 "2019-08-29T11:28:15Z")
Hi!
When I try to launch paraview
```auto
./ParaView-5.7.0-RC2-MPI-Linux-Python3.7-64bit/bin/paraview
```
I get an error related to qt5:
```auto
./paraview: /home/ParaView-5.7.0-RC2-MPI-Linux-Python3.7-64bit/bin/../lib/libQt5Core.so.5: version `Qt_5.12' not found (required by /usr/lib64/libQt5Network.so.5)
./paraview: /home/ParaView-5.7.0-RC2-MPI-Linux-Python3.7-64bit/bin/../lib/libQt5Core.so.5: version `Qt_5.12.4_PRIVATE_API' not found (required by /usr/lib64/libQt5Network.so.5)
```
I already installed many qt packages:
```auto
$ sudo dnf install qt qt-devel qt5 qt5-devel qt5-qtbase qt5-qtbase-devel
```
What am I missing…? ☹
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [August 29, 2019, 11:43am UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/2 "2019-08-29T11:43:12Z")
ParaView binaries come with their own Qt. It should not be loading `/usr/lib64/libQt5Network.so.5` but the one provided by ParaView package itself. Do you have `LD_LIBRARY_PATH` or some such environment variable set?
try running paraview as
> LD\_DEBUG=libs …/paraview
and then inspect the log to see why /usr/lib64/libQt5Network.so.5 is being loaded. That may shed some light on the issue.
---
### Author:  [@amivaleo](https://discourse.paraview.org/u/amivaleo)
#### Post date: [August 29, 2019, 12:36pm UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/3 "2019-08-29T12:36:18Z")
I tried your command. I get a very long output.
The last lines are:
4639: trying file=/home/jimmy/.paraview/lib/libvtkh5part-pv5.7.so.1
4639:
4639: /home/jimmy/.paraview/bin/…/lib/libQt5Core.so.5: error: version lookup error: version `Qt_5.12' not found (required by /usr/lib64/libQt5Network.so.5) (continued) ./paraview: /home/jimmy/.paraview/bin/../lib/libQt5Core.so.5: version`Qt\_5.12’ not found (required by /usr/lib64/libQt5Network.so.5)
4639: /home/jimmy/.paraview/bin/…/lib/libQt5Core.so.5: error: version lookup error: version `Qt_5.12.4_PRIVATE_API' not found (required by /usr/lib64/libQt5Network.so.5) (continued) ./paraview: /home/jimmy/.paraview/bin/../lib/libQt5Core.so.5: version`Qt\_5.12.4\_PRIVATE\_API’ not found (required by /usr/lib64/libQt5Network.so.5)
Yes, I have a few variables in my bashrc:
```
export MCTOOLS="$HOME/.mc-tools/mctools/"
export PATH="$HOME/.local/bin:$HOME/.MCNP6/MCNP_CODE/bin:$MCTOOLS/mcpl:$PATH"
export PYTHONPATH="$MCTOOLS/mcnp:$MCTOOLS/mcpl/src/python:$PYTHONPATH"
export DATAPATH="$HOME/.MCNP6/MCNP_DATA/"
export ISCDATA="$HOME/.MCNP6/MCNP_CODE/MCNP620/Utilities/ISC/data"
export LD_LIBRARY_PATH="/usr/lib64/:$LD_LIBRARY_PATH"
source $HOME/.root/bin/thisroot.sh
```
The LD\_LIBRARY\_PATH shouldn’t give any problem…
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 29, 2019, 12:53pm UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/4 "2019-08-29T12:53:42Z")
The `LD_LIBRARY_PATH` does cause problems because it means that all of our shipped libraries are lower precedence than your system libraries. There shouldn’t be any need to add `/usr/lib64` to this manually; that’s a distro thing.
---
### Author:  [@amivaleo](https://discourse.paraview.org/u/amivaleo)
#### Post date: [August 29, 2019, 12:58pm UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/5 "2019-08-29T12:58:10Z")
Ok.
I’ve just deleted the entire row about LD\_LIBRARY\_PATH from my bashrc.
I’ve reloaded that bashrc.
I get the same errore when trying to launch `./paraview` ☹
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [August 29, 2019, 1:03pm UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/6 "2019-08-29T13:03:24Z")
Please confirm that your `LD_LIBRARY_PATH` is indeed unset. Try `echo $LD_LIBRARY_PATH`.
---
### Author:  [@amivaleo](https://discourse.paraview.org/u/amivaleo)
#### Post date: [August 29, 2019, 1:51pm UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/7 "2019-08-29T13:51:15Z")
I’ve tried this:
```
$ unset LD_LIBRARY_PATH
$ ./paraview
```
Now it works.
Still, this shouldn’t be the right approach.
This is what I get now after removing any line about this variable from the bashrc:
```
$ echo $LD_LIBRARY_PATH
/home/jimmy/.root/lib:/usr/lib64/:/home/jimmy/.paraview/lib:
```
That seems to cause the error messages for which I opened this thread.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 29, 2019, 3:38pm UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/8 "2019-08-29T15:38:38Z")
Having a system path in LD\_LIBRARY\_PATH seems very wrong no matter how it gets there. It overrides the paths ParaView uses to use its own libraries in the package and we cannot guard against it (by the time `paraview` has executed, a bad `LD_LIBRARY_PATH` has already done its damage).
---
### Author:  [@amivaleo](https://discourse.paraview.org/u/amivaleo)
#### Post date: [August 29, 2019, 3:43pm UTC](https://discourse.paraview.org/t/failed-to-use-on-fedora-30/2484/9 "2019-08-29T15:43:11Z")
It looks like I had to reboot in order to make the changes to bashrc permanent! o.o
I usually only give
`$ source ~/.bashrc`
but this time, it kept loading the old LD\_LIBRARY\_PATH.
Weird.
Anyway, now paraview works! Thank you for your help, guys! 🙂