2009/6/26 Varun Hiremath varunhirem...@gmail.com:
Hi Rodrigo,
On Tue, 12 May, 2009 at 06:21:48PM +0200, Rodrigo Valiña Gutiérrez wrote:
Package: mayavi2
Version: 3.2.0-1
Severity: important
1) wxPython apps using mayavi2 work well, but when I close the window, it
reports a crash. Below is the output of the first case:
$ python /usr/share/doc/mayavi2/examples/mayavi/wx_embedding.py
(python:6883): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
`!GTK_WIDGET_REALIZ$
The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 4055 error_code 9 request_code 136 minor_code 9)
(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.)
I can't reproduce this bug with the latest mayavi2 3.2.0-3 package in
sid. Could you please check if it works for you? Also make sure you
get the latest version of python-vtk 5.2.1-6.
Thanks,
Varun
hi, Varun
now i tried in another computer and the bug is present, the warning is
displayed.
maybe it is an OpenGL / VTK / WxWidgets bug ?
i also observed that python-vtk with wxpython has the same or similar bug:
having some vtk scenes in a wx.Notebook, and closing all pages, makes
application crash.
it does not crash when doing the same in a wx.aui.Notebook.
$ python /usr/share/doc/mayavi2/examples/mayavi/wx_embedding.py
(python:16598): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
`!GTK_WIDGET_REALIZED (widget)' failed
The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 3089 error_code 9 request_code 136 minor_code 9)
(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.)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
