# qtconfig qtconfig: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed. Aborted Stacktrace: #0 0x00002ab335c9e395 in raise () from /lib64/libc.so.6 #1 0x00002ab335c9f7f0 in abort () from /lib64/libc.so.6 #2 0x00002ab335c97a76 in __assert_fail () from /lib64/libc.so.6 #3 0x00002ab3361b5818 in xcb_xlib_lock () from /usr/lib64/libxcb-xlib.so.0 #4 0x00002ab3348679b5 in QWidget::inputMethodEvent () from /usr/lib64/libX11.so.6 #5 0x00002ab334856d3e in XQueryExtension () from /usr/lib64/libX11.so.6 #6 0x00002ab33484ba54 in XInitExtension () from /usr/lib64/libX11.so.6 #7 0x00002ab33461872e in XextAddDisplay () from /usr/lib64/libXext.so.6 #8 0x00002ab333531b83 in _XiGetExtensionVersion () from /usr/lib64/libXi.so.6 #9 0x00002ab333531cd5 in XGetExtensionVersion () from /usr/lib64/libXi.so.6 #10 0x00002ab332794a88 in QWidget::inputMethodEvent () from /usr/lib64/libQtGui.so.4 #11 0x00002ab332744f39 in QApplicationPrivate::construct () from /usr/lib64/libQtGui.so.4 #12 0x00002ab332745d62 in QApplication::QApplication () from /usr/lib64/libQtGui.so.4 #13 0x000000000040c754 in QWidget::inputMethodEvent () #14 0x00002ab335c8b944 in __libc_start_main () from /lib64/libc.so.6 #15 0x000000000040bd29 in QWidget::inputMethodEvent () #16 0x00007fff792e7d98 in ?? () #17 0x0000000000000000 in ?? ()
I believe this is a duplicate of bug #8581. If upgrading to libXi 1.1.0 doesn't fix the problem for you, please re-open this bug. *** This bug has been marked as a duplicate of 8581 ***
Thanks. I'll verify with libXi 1.0.2 + git patches: - Don't call XInput_find_display in _XiGetExtensionVersion, while the Display lock is held. (2006-10-15 09:03:57) - Bug #8663: _XiCheckExtInit must drop the Display lock in all error cases. (2006-11-19 10:04:26) The patch - Don't call XInput_find_display in _XiCheckExtInit, while the Display lock is held. (2006-10-15 06:26:21) is already included in libXi 1.0.2.
Yes, this fixes the issue. :-)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.