Paraview on Fedora 36 does not start.

ParaView Support
1

Apologies if this is not the right place for the following query (I’m a novice user of ParaView).
I did a fresh install of Fedora 36 (from scratch) and then I installed ParaView in two ways:

a) Via dnf --best install, but then it fails to launch due to a graphic issue:
paraview [1] 3087 paraview: symbol lookup error: /usr/bin/…/lib64/paraview/libvtkFiltersParallelDIY2.so.1: undefined symbol: _ZN20vtkDIYGhostUtilities29InflateBoundingBoxIfNecessaryEP11vtkPolyDataPKdR14vtkBoundingBox

b) Then I tried with ParaView-5.10.1-MPI-Linux-Python3.9-x86_64.tar.gz from https://www.paraview.org/paraview-downloads, but the error now is:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.

The whole Fedora system, in particular the Qt plataform, was installed using the dnf --best command.
I attach a log file with some info.
Please, any suggestions to correct it? Thanks in advance.

Regards.
Jorge.
gnome-wayland.log (20.4 KB)

2

Hi,

For the b case, may be libxcb is not installed ?

ldd
/home/test/TMP/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/plugins/platforms/libqxcb.so

should show any missing libraries ?

dnf install libxcb may be enough to install them.

For info, ParaView-5.10.1-MPI-Linux-Python3.9-x86_64.tar.gz is
working on my workstation running Fedora 36.

Regards,
Pierre TURLAIS

3

Dear Pierre,
Good point but without luck:
$ sudo dnf --best install libxcb
Last metadata expiration check: 0:35:57 ago on Sat 06 Aug 2022 16:28:15 -03.
Package libxcb-1.13.1-9.fc36.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Just in case, how should the LD_LIBRARY_PATH environment variable be defined?
Next, I’ll look at the output of ldd to look for other missing libraries.
Ok, if ParaView-5.10.1-MPI-Linux-Python3.9-x86_64.tar.gz is working on your workstation running Fedora 36, then I have something missing.
Thanks for you reply.
Regards.
Jorge.

4

Om my machine, from directory ParaView-5.10.1-MPI-Linux-Python3.9-x86_64

ldd plugins/platforms/libqxcb.so | fgrep xcb
libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x00007f8558694000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f8558664000)
libxcb-xkb.so.1 => /lib64/libxcb-xkb.so.1 (0x00007f8557e94000)
rpm -qf /lib64/libX11-xcb.so.1 /lib64/libxcb.so.1 /lib64/libxcb-xkb.so.1
libX11-xcb-1.7.3.1-2.fc36.x86_64
libxcb-1.13.1-9.fc36.x86_64
libxcb-1.13.1-9.fc36.x86_64

So maybe the package libX11-xcb is missing and dnf install libX11-xcb
should help.

ldd plugins/platforms/libqxcb.so | fgrep ‘not found’

should give any missing library.

I dont think you need to use LD_LIBRARY_PATH except if you want to
access libraries with unusual path.

Regards,
Pierre TURLAIS

5

Dear Pierre,

I still can’t find it:

a) sudo dnf --best install libX11-xcb
Last metadata expiration check: 1:08:18 Aug on Sat 06 Aug 2022 16:28:15 -03.
Package libX11-xcb-1.7.3.1-2.fc36.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

On my machine, from directory ParaView-5.10.1-MPI-Linux-Python3.9-x86_64:

ldd plugins/platforms/libqxcb.so | fgrep xcb
libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x000014f74984b000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x000014f74981f000)
libxcb-icccm.so.4 => /usr/lib64/libxcb-icccm.so.4 (0x000014f748fdc000)
libxcb-image.so.0 => /usr/lib64/libxcb-image.so.0 (0x000014f748fd6000)
libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x000014f748fd1000)
libxcb-keysyms.so.1 => /usr/lib64/libxcb-keysyms.so.1 (0x000014f748fcc000)
libxcb-randr.so.0 => /usr/lib64/libxcb-randr.so.0 (0x000014f748fb9000)
libxcb-render-util.so.0 => /usr/lib64/libxcb-render-util.so.0 (0x000014f748fb0000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x000014f748fa0000)
libxcb-shape.so.0 => /usr/lib64/libxcb-shape.so.0 (0x000014f748f9a000)
libxcb-sync.so.1 => /usr/lib64/libxcb-sync.so.1 (0x000014f748f90000)
libxcb-xfixes.so.0 => /usr/lib64/libxcb-xfixes.so.0 (0x000014f748f86000)
libxcb-xinerama.so.0 => /usr/lib64/libxcb-xinerama.so.0 (0x000014f748f81000)
libxcb-xkb.so.1 => /usr/lib64/libxcb-xkb.so.1 (0x000014f748f61000)
libxcb-xinput.so.0 => /usr/lib64/libxcb-xinput.so.0 (0x000014f748f3b000)
libxcb-util.so.1 => /usr/lib64/libxcb-util.so.1 (0x000014f74829b000)

b) A search for the missing symbols indicates nothing:

ls -all plugins
drwxr-xr-x. 1 jdelia jdelia 160 Mar 14 14:54 plugins
ldd plugins/platforms/libqxcb.so | fgrep ‘not found’

c) LD_LIBRARY_PATH: ok, there are no libraries with unusual path.

Regards,
Jorge.

6

OK,

Maybe the variable QT_DEBUG_PLUGINS will give more info.
export QT_DEBUG_PLUGINS=1
before lauching paraview

Regards,
Pierre TURLAIS

7

SOLVED. The bug was that, after installing Fedora 36, an outdated user PATH had been reused, instead of appending the user definitions to the new Fedora 36 default PATH. Advice: pay attention to the user environment in the updates, upgrades, or migrations.
Thank you very much for your assistance.
Regards.
Jorge.

8

Hi,

I was wondering if you can elaborate on what you did for a solution? I am having the same problem on a fresh install of Fedora 37, and I am not sure how it is possible that an old PATH got reused.

Thanks