[Python-apps-team] Bug#499580: Bug#499580: Bug#499580: Bug#499580: mayavi2: please pack a new release (filed instead of crashes in explore())

[Varun Hiremath]

Hi Yaroslav,

On Wed, 01 Oct, 2008 at 01:02:48AM -0400, Yaroslav Halchenko wrote:
> Thanks for the update. Indeed NEW is not too fast -- I myself
> waiting on my new package to pass through ;)
> 
> I hope that there would be no major licensing issues... May be it is
> worth to pursue unstable right away? who needs prev version could get it
> from lenny ;)
> 
> few brief issues I ran into
> 
> * trying to run examples (from /usr/share/doc/mayavi2/examples/mayavi)
> 
> ** $> python offscreen.py 
> Failed to initialize TTM buffer manager.  Falling back to classic.
> ERROR: In /build/buildd/vtk-5.0.4/IO/vtkPNGWriter.cxx, line 220
> vtkPNGWriter (0x67d0db0): Unable to open file offscreen.png
> 
> ERROR: In /build/buildd/vtk-5.0.4/IO/vtkImageWriter.cxx, line 506
> vtkPNGWriter (0x67d0db0): Ran out of disk space; deleting file(s) already written
> 
> $> dpkg -S offscreen.png
> dpkg: *offscreen.png* not found.

This is just a write permission issue (though I have no idea about
this misleading error message), the offscreen.png file is dumped by
the offscreen.py script. So try to run it some directory where you
have write access (say $HOME) instead of /usr/share/doc/...

> 
> ** was 'explore' function removed from interactive shell within mayavi2?
> 
> ** Also I am observing major rendering bug (or some feature? :-)), which
> I am not sure I experienced with sid version that badly... screenshot of
> running contour.py http://www.onerussian.com/tmp/mayavi2-zorder.png
> Similar incorrect renders happen in other scripts (numeric_source.py).
> 
> I guess I would need to test on some other box to check if that is not a card
> specific issue.

I'm also facing some rendering issues. I will check this with upstream
and get back to you.

-Varun