[Paraview] GLXBadContext error when saving to png file

[Berk Geveci]

I am guessing this is an OpenGL driver bug. We are using OpenGL
framebuffers for offscreen rendering when available. Some drivers
claim framebuffers are supported and die horribly when they are used.
Try this:

 view.UseOffscreenRenderingForScreenshots = 0

before the WriteImage() call.

-berk

On 2/22/08, Ondrej Certik <ondrej at certik.cz> wrote:
> Hi,
>
>  when I try to save the image from paraview, I always get a
>  GLXBadContext X error. This also occurs when saving from Python, so
>  here
>  is a simple script to reproduce the problem:
>
>  $ cat t.py
>  from paraview import servermanager as sm
>  sm.Connect()
>  view = sm.CreateRenderView()
>  view.StillRender()
>  view.WriteImage("image.png", "vtkPNGWriter", 1)
>  $ python2.5 t.py
>  X Error of failed request:  GLXBadContext
>   Major opcode of failed request:  159 (GLX)
>   Minor opcode of failed request:  5 (X_GLXMakeCurrent)
>   Serial number of failed request:  24
>   Current serial number in output stream:  24
>
>
>  This happens both with the official binary, and when built from
>  source. I use Debian, with Intel 945GM graphic card.
>
>  Otherwise everything works fine. We are in the process of creating a
>  Debian package for paraview and getting it into Debian (and Ubuntu),
>  we already managed to built it with MPI and Python. If you use Debian,
>  you can use it from:
>
>  svn://svn.debian.org/svn/pkg-scicomp/paraview/
>
>  (it will take at least a month or more before it gets into Debian unstable).
>
>  Ondrej
>  _______________________________________________
>  ParaView mailing list
>  ParaView at paraview.org
>  http://www.paraview.org/mailman/listinfo/paraview
>