Package Details: paraview 5.1.2-1

Git Clone URL: (read-only)
Package Base: paraview
Description: Parallel Visualization Application using VTK
Upstream URL:
Licenses: custom
Submitter: stephane
Maintainer: deezy
Last Packager: deezy
Votes: 57
Popularity: 1.964170
First Submitted: 2012-12-11 01:37
Last Updated: 2016-08-04 00:02

Latest Comments

NOhs commented on 2016-09-17 22:51

@maintainer: Paraview release notes say: "ParaView now comes with a built in ray traced rendering capability." Which is a reference to the new OSPray feature. Will this be added in a future update of this package? As OSPray comes with the default compiled versions I think the package in the AUR called "paraview" should probably stick to the default and include it. Would be awesome :).

ugis commented on 2016-08-15 11:17

Hi everyone,

I have successfully installed the paraview on my laptop, however, I have an issue with openGL rendering. Everything works overall, but surface of a given body is randomly transparent - i.e., parts of the surface seem transparent, such that part of the body can be seen from inside.

Could this be bug of the package build? I have checked openGL rendering using glxgears and unigine-heaven, and I don't see any problems there.


melanopsis commented on 2016-06-20 23:00

This won't compile for me without the qt5-x11extras package

deezy commented on 2016-06-02 14:57

hdf5 (1.8.x) is included in the paraview source and is used as long hdf5-1.10.x (in Extra) and paraview/vtk are not really compatible.
With the next release, the new Extra package hdf5_18 may be used. But I have to test this first.
So at the moment there is no missing dependency.

hiaselhans commented on 2016-06-02 13:17

missing dependency: hdf5

lahwaacz commented on 2016-05-09 17:10

I'm not getting the 8th line:

deezy commented on 2016-05-09 16:03

@lahwaacz @juliohm
Added the Exec key to the desktop file. Should work now.

lahwaacz commented on 2016-05-09 15:34

See the specification:

"The Exec key is required if DBusActivatable is not set to true."

So the paraview.desktop does not comply to the standard.

juliohm commented on 2016-05-09 14:59

Everything is perfect, except the desktop file created under /usr/share/applications/paraview.desktop. When I try to open paraview from the Gnome menu it is not found with the message "Desktop file didn't specify Exec field". What is the exact difference between Exec and TryExec? Why to opt for the latter?

wilmbas commented on 2016-05-07 09:43

Build fails with recent version 6 of GCC. I am newbie in pushing updated .SRCINFO and modified PKGBUILD's. But patch and sha1sum is created and added to it. Since I failed to push it please find the patch concatenated to this comment. (Luckily, since I missed to have correct path strings towards VTK/CMake in my patch...newbie behaviour, sorry!)

Have fun, nice weekend. Regards wilmbas

--- VTK/CMake/GenerateExportHeader.cmake 2016-05-07 10:22:52.463297686 +0200
+++ VTK/CMake/ 2016-05-07 10:20:26.030649703 +0200
@@ -166,7 +166,7 @@
execute_process(COMMAND ${CMAKE_C_COMPILER} ARGS --version
OUTPUT_VARIABLE _gcc_version_info
ERROR_VARIABLE _gcc_version_info)
- string(REGEX MATCH "[345]\\.[0-9]\\.[0-9]*"
+ string(REGEX MATCH "[3-9]\\.[0-9]\\.[0-9]*"
_gcc_version "${_gcc_version_info}")
# gcc on mac just reports: "gcc (GCC) 3.3 20030304 ..." without the
# patch level, handle this here:
--- VTK/CMake/vtkCompilerExtras.cmake 2016-05-07 10:23:05.523533858 +0200
+++ VTK/CMake/ 2016-05-07 10:22:03.425744259 +0200
@@ -32,7 +32,7 @@
OUTPUT_VARIABLE _gcc_version_info
ERROR_VARIABLE _gcc_version_info)

- string (REGEX MATCH "[345]\\.[0-9]\\.[0-9]*"
+ string (REGEX MATCH "[3-9]\\.[0-9]\\.[0-9]*"
_gcc_version "${_gcc_version_info}")
if(NOT _gcc_version)
string (REGEX REPLACE ".*\\(GCC\\).*([34]\\.[0-9]).*" "\\1.0"

All comments