# Paraview 5.9 from website not working in F33?

**URL:** https://discourse.paraview.org/t/paraview-5-9-from-website-not-working-in-f33/6461
**Category:** ParaView Support
**Created:** [February 14, 2021, 7:02am UTC](https://discourse.paraview.org/t/paraview-5-9-from-website-not-working-in-f33/6461 "2021-02-14T07:02:44Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Root-voidX](https://discourse.paraview.org/user_avatar/discourse.paraview.org/root-voidx/32/5084_2.png) [@Root-voidX](https://discourse.paraview.org/u/Root-voidX)
#### Post date: [February 14, 2021, 7:02am UTC](https://discourse.paraview.org/t/paraview-5-9-from-website-not-working-in-f33/6461/1 "2021-02-14T07:02:45Z")

</div>

Hello everyone,

I noticed something with paraview on Fedora 33. It errors out with segfault, while when I ran it inside a Fedora 32 docker, it ran fine.

This is the error:

```auto
 SI  localhost  ~  Downloads/ParaView-5.9.0-RC4-MPI-Linux-Python3.8-64bit/bin/paraview
( 2.498s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.498s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.647s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.647s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.647s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.647s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.665s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.665s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.711s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.711s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.711s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.711s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.711s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.711s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.729s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.729s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.729s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.729s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.729s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.729s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.737s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.737s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.737s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.737s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.737s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.737s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.752s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.753s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.753s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.753s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.753s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.753s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.760s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.760s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.760s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.760s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.760s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.760s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device

Loguru caught a signal: SIGSEGV
Stack trace:
0 0x7f0bd152ca60 /lib64/libc.so.6(+0x3da60) [0x7f0bd152ca60]
( 3.794s) [paraview] :0 FATL| Signal: SIGSEGV
error: exception occurred: Segmentation fault

```

Anyone know why this happens on Fedora 33?

---

<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: [February 15, 2021, 3:21pm UTC](https://discourse.paraview.org/t/paraview-5-9-from-website-not-working-in-f33/6461/2 "2021-02-15T15:21:04Z")

</div>

Hmm. The VIsRTX noise is probably just that: noise. Could you get a backtrace from `gdb` perhaps? That said, I’m running Fedora 33…and it launches fine after installing `libxcrypt-compat`. So the `gdb` backtrace would be useful here.

---

<div class="post-metadata">

### Author: ![Root-voidX](https://discourse.paraview.org/user_avatar/discourse.paraview.org/root-voidx/32/5084_2.png) [@Root-voidX](https://discourse.paraview.org/u/Root-voidX)
#### Post date: [March 11, 2021, 10:02am UTC](https://discourse.paraview.org/t/paraview-5-9-from-website-not-working-in-f33/6461/3 "2021-03-11T10:02:37Z")

</div>

I uninstalled and reinstalled libxcrypt-compat, and paraview launched. I don’t know why the uninstall was required though.