forwarded 534764 https://svn.enthought.com/enthought/ticket/1824 thanks
Hi Kevin, On Fri, 26 Jun, 2009 at 06:08:59PM -0700, Kevin Mitchell wrote: > ipython -wthread > > and at the prompt the following commands > > from enthought.mayavi import mlab,api > mlab.test_surf() > > upon which I see > """ > The program 'python' received an X Window System error. > This probably reflects a bug in the program. > The error was 'GLXBadContext'. > (Details: serial 63 error_code 154 request_code 143 minor_code 5) > ... > """ > and I'm dumped back to the command prompt > > I've found that one workaround is to manually start the engine first: > > from enthought.mayavi import mlab,api > api.Engine().start() > mlab.test_surf() > > will give me a working figure. > > This workaround does not however work for the OffScreenEngine: > > from enthought.mayavi import mlab,api > api.OffScreenEngine().start() > mlab.test_surf() Thanks for the report. For me only the OffScreenEngine doesn't work, but the regular mode works fine and I am able to see the popup window. I have forwarded your report upstream: https://svn.enthought.com/enthought/ticket/1824 Thanks, Varun ------------------------ $$ ipython -wthread Python 2.5.4 (r254:67916, Feb 18 2009, 03:00:47) Type "copyright", "credits" or "license" for more information. IPython 0.8.4 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object'. ?object also works, ?? prints more. In [1]: from enthought.mayavi import mlab,api In [2]: mlab.test_surf() Failed to initialize GEM. Falling back to classic. (python:20034): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed Out[2]: <enthought.mayavi.modules.surface.Surface object at 0x7f59830> In [3]: api.OffScreenEngine().start() In [4]: mlab.test_surf() Failed to initialize GEM. Falling back to classic. The program 'python' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadCurrentWindow'. (Details: serial 145 error_code 171 request_code 153 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ------------------------ -- Varun Hiremath http://eccentric.mae.cornell.edu/~vh63/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
