I'm tracking this down. Goodwin, I was able to reproduce the issue using the steps listed on http://paraview.org/Bug/view.php?id=12424 I'll keep the list updated as I discover things.
Utkarsh On Mon, Dec 5, 2011 at 2:27 PM, Seth Gilchrist <[email protected]> wrote: > Hi all, > This seems to be a recurring problem. Below are some links to previous > posts in the PV mailing list with the same issue. > > It seems to be a fairly widespread bug. I have tried compiling from the git > and releases and tried all the binaries. The only way around is to go back > to 3.8 or earlier (one post said they had to go back to 3.6). > > Cheers, > Seth > > http://www.paraview.org/pipermail/paraview/2011-October/022868.html > > http://www.paraview.org/pipermail/paraview/2011-October/022892.html > > http://www.mail-archive.com/[email protected]/msg13286.html > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
