Me too, I’m using the binary release from https://paraview.org/download
If it’s not an inconvenience for you, given the fact that you are already using Arch, could you try to install the stable 5.11.2 version that is in the Arch repositories? I really can’t understand what is happening in my system which seems, for the rest, to be working fine.
If it is not possible for you, never mind.
Thank you.
I confirm that this is not working with paraview package from archlinux package manager.
Looks like an issue with the XML parser, which is using system expat in your case and which is not the case of the binary release.
You may want to open an issue on the arch linux package itself and link to this discussion.
1 Like
Thank you, I asked for a username and password to file a bug for the Arch Linux package. Apparently for spam reason you have to request an account by mail. I will then post a bug and link this thread. I will report here if it is fixed or not.
As an adidtional piece of information, I’m having the same issue in Debian testing/unstable, also with ParaView 5.11.2(+dfsg-6+b1) and libexpat1 2.6.0-1 (not sure which version of libexpat is being used by Arch). I’ll report the issue to Debian and link to this thread.
1 Like
BTW I tried downgrading libexpat1 on my Debian installation to 2.5.0-2+b2 and it solved the issue for me, which seems to confirm that the issue is in the expat library rather than in ParaView itself.
2 Likes
The expat version I am using now, which causes the problem, is:
core/expat 2.6.1-1 (116.3 KiB 414.4 KiB) (Installed)
An XML parser library
So it is a bug with libexpat 2.6, not with Paraview, right?
Maybe Paraview binary version 5.12-RC is using libexpat 2.5?
Yes, ParaView 5.12.0 is using expat 2.5: https://gitlab.kitware.com/paraview/common-superbuild/-/blob/6999b3a595e1816f40e8018e8ee1aa97c1783452/versions.cmake#L646
Thank you, if I understand it correctly, Arch Linux tries to compile ParaView against the system version of expat which has this issue. But maybe the problems is related to vtk too from what I can understand reading the bug report in Arch here (I tried to file the bug but they didn’t provide me an account, I wrote them a week ago, but luckily someone filed it for me. 
)
Maybe a useful information: Paraview 5.12 has been released in Arch Linux and the problem is still here. I think Arch Linux developers are not that keen on using the internal version of the package libraries in general. In our case the internal version is expat 2.5 but the Arch Linux package build is linked against the expat system version (2.6.1) which causes the bug.
Which is expected of ArchLinux. We need to fix it.
I have a question/curiosity, I’m not an expert at all. Paraview does not require a specific version of expat for particular reasons, right? Are you using expat 2.5 because it was the latest release when you started to write the code for Paraview 5.12?
By the way I think that if the problem is expat maybe expat developers have to fix the bug, I don’t know if it would be easier for us Arch Paraview user to use in the meantime the binary package downloadable from the Paraview website.
edit: I have just read that the bug is on VTK and someone is working to solve it.
Yes, exactly so: https://gitlab.kitware.com/paraview/common-superbuild/-/commit/6744ee3df360a374ec66f0793def67b379aca8c3
expat 2.6.0 came out just about a month before ParaView 5.12.0.
While I wait for the bug to be fixed, I am trying to install the binary version from the Paraview website.
I am using Arch Linux like you, but how can I install it? Simply running the executable does not work.
I downloaded that archive and I extracted it, but what executable should I run?
For example
./paraview
/home/massimo/Dottorato/Paraview/ParaView-5.12.0-MPI-Linux-Python3.10-x86_64/bin/paraview-real: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
sudo pacman -S libxcrypt-compat
1 Like
Thank you, it works. I don’t know why that package is not a dependency for the Arch Linux pkgbuild (it should be already installed otherwise) but it doesn’t really matter.
Because the binary release use an old version of libxcrypt