I am guessing that this may be related to some changes Utkarsh and Amy have been making. Utkarsh, can you check when the HAVS renderer was added? Kevin could try to update to before then and see if this fixed the problem. Also, can you try the CVS version of Mesa, Kevin? We have reported a bug to the Mesa group that they fixed. I don't think it relates to this particular problem but it is worth a try. As soon as I have some time, I will try with mesa as well.
<br><br>-berk <br><br><div><span class="gmail_quote">On 9/20/06, <b class="gmail_sendername">Kevin H. Hobbs</b> <<a href="mailto:hobbsk@ohiou.edu">hobbsk@ohiou.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, 2006-09-20 at 09:48 -0400, Kent Eschenberg wrote:<br>> We've been using osmesa with ParaView on a Tru64 system for over a year and I haven't seen those problems. The most recent version we've installed is 2.4.4
. Contact me directly if you would like details.<br>><br>> Kent<br>> Pittsburgh Supercomputing Center<br><br>I think this started for me sometime late this summer in the CVS<br>development version.<br><br><br>_______________________________________________
<br>ParaView mailing list<br><a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br><a href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a><br><br><br>
<br></blockquote></div><br>