Paraview 5.9 from website not working in F33?

ParaView Support
1

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:

 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?

2

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.

3

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