Paraview 3.12 on 64-bit CentOS 5.7

I finally got around to installing Paraview on my CentOS 5 box.  There are no official RPMS for CentOS 5, so I was expecting a painful build process. To my great surprise, I was able to download the Paraview binary for Linux (64-bit) from Kitware, unpack the archive, and run it!  As root, I placed the entire ParaView-3.12.0 directory under /opt/Paraview.  You could also keep it in your home directory if you are running a single-user system.  I added /opt/Paraview/ParaView-3.12.0/bin to the $PATH in the .bashrc file in my home directory.  Now I can type paraview at the command line and it runs!
What if you want Paraview to appear in the Applications menu in your desktop environment?  Most modern desktops (I use XFCE4) construct the Applications menu “on the fly” based upon the files in a standard directory (/usr/share/applications on CentOS).  The Free Desktop Project has created a standard for desktop entry files.  You may also find this summary of the standard to be helpful.  To add Paraview to the menu, you simply need to create a new file in the standard location.  If you installed Paraview in your user directory, you may want to place the desktop file in $HOME/.local/applications.  Here are the contents of a file I called paraview.desktop:

[Desktop Entry]
Comment=3D visualization tool

I found Paraview menu icons here.  Save the SVG icon to /usr/share/icons (there may be an equivalent location in your user directory but I don’t know what it is).  Now, when you bring up the Applications menu in your desktop environment the entry should appear (no need to restart or anything).

Screenshot of Paraview

3 thoughts on “Paraview 3.12 on 64-bit CentOS 5.7”

  1. hello , i have installed paraview in Red Hat 4.4.6-3,but when i enter paraview ,it return vtkXOpenGLRenderWindow (0x2200b00): GLX not found. Aborting. i wish you can help me . thanks ! my email is

  2. Erick,
    Wenghuih and I emailed back and forth a few times and I made a few suggestions, but he never told me if/how he solved the problem. I think his problem was that he was trying to connect to ParaView on a remote machine and the X connection wasn’t configured correctly. Are you installing ParaView on a local or remote machine? Can you run other X applications?

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.