The patch seems to have resolved the issue related to the DISPLAY
variable. Thanks!
Utkarsh Ayachit wrote:
Looks like the patch should resolve this issue. I've committed it to
CVS. Let me know if that doesn't work. We'll commit it to 3.8 branch
soon.
Utkarsh
On Wed, Apr 7, 2010 at 2:20 PM, U
It is now in the branch as well.
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMChartViewProxy.cxx,v
<-- Servers/ServerManager/vtkSMChartViewProxy.cxx
new revision: 1.8.2.1; previous revision: 1.8
On Wed, Apr 7, 2010 at 2:43 PM, Utkarsh Ayachit wrote:
> Looks like the patch should re
Looks like the patch should resolve this issue. I've committed it to
CVS. Let me know if that doesn't work. We'll commit it to 3.8 branch
soon.
Utkarsh
On Wed, Apr 7, 2010 at 2:20 PM, Utkarsh Ayachit
wrote:
> Rick/ Carrie,
>
> My paraview is still building and will be a while before I can try
>
Rick/ Carrie,
My paraview is still building and will be a while before I can try
this out. But attached is a patch that I think will solve this issue.
Can you try it out?
Thanks
Utkarsh
On Wed, Apr 7, 2010 at 2:15 PM, Utkarsh Ayachit
wrote:
> I was writing a response when it struck me, are you
I was writing a response when it struck me, are you building with
PARAVIEW_BUILD_QT_GUI ON? That's possible the only difference between
your build and mine. I am going to turn on PARAVIEW_BUILD_QT_GUI and
try to reproduce the problem.
Utkarsh
On Wed, Apr 7, 2010 at 2:06 PM, Rick Angelini wro
So, we're really stumped.
- Paraview (pvbatch) 3.6.2 works exactly as we'd expect.
- pvbatch 3.8.0/3.9.0 fail with the "can't open display" error. If we
set a display variable, pvbatch works, but that's not really a solution.
- All three are using the same exact Mesa library and use the same
C
That's exactly what I am doing as well ("unset DISPLAY" that is), and
seems to work well. Is this a debug build. Can you track down where
the error message is coming from? I am not sure where this error
message is coming from since it doesn't look like a paraview message
and a quick "grep" didn't
Utkarsh,
When I do an ldd pvbatch appears to be using the correct libraries GL
libraries (I am building agains mesa-7.0.4, could it be that my version
of mesa is too old). I ran the following test:
bash-3.2$ echo $DISPLAY
:0.0
bash-3.2$ unset DISPLAY
bash-3.2$ echo $DISPLAY
bash-3.2$ mpirun
Carrie,
I just tried it with CVS ParaView and I could not reproduce it. Can
you reproduce this when running on a single node? Try running ldd on
pvbatch, is it getting the right OpenGL libraries?
Utkarsh
On Wed, Apr 7, 2010 at 9:40 AM, Utkarsh Ayachit
wrote:
> That sounds fishy, let me take a l
That sounds fishy, let me take a look. I'll get back to you.
Utkarsh
On Wed, Apr 7, 2010 at 8:06 AM, Carrie E. Spear (Cont, CISD/ARL)
wrote:
> Good Morning,
>
> I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when
> trying to use pvbatch and offscreen rendering. When I run wi
Good Morning,
I am currently having issues with paraview-3.8.0 and paraview-3.9.0 when
trying to use pvbatch and offscreen rendering. When I run with my
DISPLAY variable set, I don't have any issues, when the DISPLAY variable
is not set it fails with the "cannot connect to X server error". I h
11 matches
Mail list logo
