Hello, all.
I have just downloaded the new Paraview 3.14 binaries fort Linux 64 bits
on the Paraview software page.
PV 3.14 can be launched on Linux 64 bits CentOS 5.7, but it crashes when
I select either the Open item or the Load state item in the File menu!
Has anybody the same problem ?
Richard GRENON a écrit :
PV 3.14 can be launched on Linux 64 bits CentOS 5.7, but it crashes
when I select either the Open item or the Load state item in the
File menu!
Hello.
I just want to add that both 32 bit and 64 bit versions of PV 3.14 crash
when trying to open a file.
Not yet
On Thursday 23 February 2012 14:04:53 Richard GRENON wrote:
Richard GRENON a écrit :
PV 3.14 can be launched on Linux 64 bits CentOS 5.7, but it crashes
when I select either the Open item or the Load state item in the
File menu!
Hello.
I just want to add that both 32 bit and 64 bit
Hi Gena.
When I launch PV 3.14 Linux from a terminal, it crashes again when I try
to open a file but I get this error message:
Cannot mix incompatible Qt libraries
Is there a Qt library missing in the PV 3.14 binaries and is PV
searching for an old one installed on my Workstation ?
But I
On 22/02/2012 17:54, Utkarsh Ayachit wrote:
Goodwin,
Thanks for the update.
Utkarsh
Here's the backtrace on the remote server:
The server has no GPU and uses OSMesa.
It's stuck in vtkSocket::Receive() too! (so is the client)
#0 0x772868a2 in recv () from /lib64/libpthread.so.0
Try running paraview as such:
LD_DEBUG=libs ./bin/paraview
The click FIle | Open and make it crash.
Look at the output generated. It should show you the libraries that it
searched for and loaded. See if you detect any Qt library mismatches.
Utkarsh
On Thu, Feb 23, 2012 at 7:37 AM, Richard
Looks like you compiled version is 3.14-RC2. Try updating. Not sure if
the issue was resolved since the RC2.
Utkarsh
On Thu, Feb 23, 2012 at 10:01 AM, Abdullahi Sanusi
scontact...@gmail.com wrote:
Hi Utkarsh,
Multiple point selection worked fine just the way it appears on the
screenshot you
The offending line is:
find library=libQtSvg.so.4 [0]; searching
7785: trying file=/usr/lib64/qt4/lib64/libQtSvg.so.4
Try the following. If that works, I'll update the binaries:
Remove files ./lib/paraview-3.14/iconengines/libqsvgicon.so and
Hi,
I am new to paraview python scripting. I wrote a script which can automate
visualization of my .vtu file. Additionally, it can zoom into the view
(which I need). Now, I need to plot the distances in x-axis y-axis only
for this zoomed part (not the whole domain). For example, if the domain is
OK, new version didn't help. So I tried to compile from source, again. After
spending another 3 hrs I got this error. I thing that's the error I got last
time.
---code start---
Building CXX object Qt/Widgets/CMakeFiles/pqWidgets.dir/pqHelpWindow.cxx.o
Your Qt is not built with WebKit. Did you build Qt from source as well?
Utkarsh
On Thu, Feb 23, 2012 at 3:13 PM, Kaster Might kastermi...@gmail.com wrote:
OK, new version didn't help. So I tried to compile from source, again. After
spending another 3 hrs I got this error. I thing that's the
I'm not sure how exactly I installed it, but most likely using yum.
Is it enough to have all files necessary?
--- code start ---
sudo yum install qt.x86_64 qtwebkit.x86_64 qtwebkit-devel.x86_64
Package 1:qt-4.6.2-20.el6.x86_64 already installed and latest version
Package
Hi Goodwin,
Did you also apply the patch on the server side? Again it may not help,
but without it if there is an error during recv the call would silently
restart and you'd never know about the error. I had a similar deadlock
as you do here with version 3.10 on our Cray XE which is how I
Hi Burlen,
I applied your patch before recompiling.
This problem is only happen on versions = 3.12 that are on
headless/gpuless servers.
I'm guessing that it's a problem with offscreen rendering on the server.
Or it could be a similar subtle bug in vtkSocket... I'll keep looking.
Thanks
My 2 cents (sorry for butting in without actually reading the full thread) -
I have noticed that states from earlier version of PV are not compatible
with 3.14 for some reason. If you resave the state then it works.
-Original Message-
From: paraview-boun...@paraview.org
Hi,
Is any one out there using ParaView client through VirtualGL and using the
default_server config?
I notice that if I launch the command below from within ParaView I only see
1 or 2 GPU's getting used (looking at load). If I run it outside of ParaView
then both GPU's have load. I am running
David's suggestion below is very good if you have many large files as
the processing will be really fast.
Using VTK you can easily adopt the following approach:
1) Develop a reader for a single file.
2) Extend it to process multiple files e.g. all files in a directory.
3) Develop a GUI to control
Hi, sorry that should read I only see 1 of 2 GPU's getting used i.e. I
have 2 GPU's and the second is ignored. Also I tested glxgears running
through VirtualGL and I can point it to either one or the other GPU and that
works. So it seems to be something with pvserver launched from a process
that
18 matches
Mail list logo