https://bugzilla.novell.com/show_bug.cgi?id=257830 ------- Comment #23 from eich@novell.com 2007-04-03 06:06 MST ------- I'm not sure if I'm interpreting the top dump correctly. But it seems as if the error handler (x_error_handler) calls XCloseDisplay(). XCloseDisplay() doen't lock itself but XFreeGC() does. However XReply() gets called in a locked context already. This doesn't look right. #4 0x00002ae906a21475 in g_str_equal () from /usr/lib64/libX11.so #5 0x00002ae9069fdb48 in XFreeGC () from /usr/lib64/libX11.so #6 0x00002ae9069f6a8c in XCloseDisplay () from /usr/lib64/libX11.so #7 0x0000000000458c5a in x_error_handler (dpy=0x3285, ee=0x3285) at x11conn.c:106 #8 0x00002ae906a1aded in _XError () from /usr/lib64/libX11.so #9 0x00002ae906a223f8 in _XReply () from /usr/lib64/libX11.so The second and third dump is a lot harder to interpret. FreePixmap() is called (a rather normal thing) which of course tries to lock the display. Above that the trace ends up in a maze of Qt functions. No idea who else locks there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.