Hi, There seem to be a lot of conflicting factoids in the reports of what is actually going wrong. Either way though, I can think of very few possibilities for wx to 'freeze' X, except through a grab gone wrong, and there shouldn't be very many possibilities for that in wx itself...
On Mon, Oct 10, 2005 at 08:24:55PM +0200, Stefan Potyra wrote: > When highlighting text (for example in the code window of gvr), dragging > and/or clicking fast on it, So you (most probably) have a race which appears to be dependent on the order in which XEvents arrive. Logging them and seeing which combination causes the trouble may be both elucidating and helpful for reproducing it on demand. > the wxpython program crashes and > doesn't release the mouse, so that complete x is "frozen". (Sometimes > keyboard still works, sometimes it doesn't.) Killing the app will > restore normal operation. Defining better what you mean by "keyboard still works" may give you some clues. There is a difference between it "not working" and just not having the focus somewhere useful. Does killing the app remotely restore the keyboard too? > (gdb) bt > #0 0xffffe410 in __kernel_vsyscall () > #1 0xb7ed20bd in poll () from /lib/tls/i686/cmov/libc.so.6 > #2 0xb7597ee6 in wxPaletteBase::wxPaletteBase () from > /usr/lib/libwx_gtk2ud_core-2.6.so.0 Everything from here up (at least) would seem completely bogus. Which leaves me to think that it is either a gtk (or lower) bug, or wx has set an invalid callback or similar, leading gtk to smash the stack. Using a debug glib and examining what you have in frame #3 below might shed some more light on things. > #3 0xb6c00348 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 > #4 0xb6c007e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 > #5 0xb7002ee5 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 > #6 0xb75b8540 in wxEventLoop::Run () from /usr/lib/libwx_gtk2ud_core-2.6.so.0 > #7 0xb7653d6b in wxAppBase::MainLoop () from > /usr/lib/libwx_gtk2ud_core-2.6.so.0 > #8 0xb7a18fed in wxPyApp::MainLoop () from hth, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
