![](https://secure.gravatar.com/avatar/0f3611b2322c6e06c8b8f68ccae38f3b.jpg?s=120&d=mm&r=g)
Hello, I've been using X11R7 for five months now and it really works like a charm :) but since the latest updates of libxcb and mesa3d i've been experiencing some problems... all them were related to xcb and binaries terminating with: programname: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed. or programname: xcb_xlib.c:41: xcb_xlib_unlock: Assertion `!c->xlib.lock' failed. of course some of these problems went away rebuilding apps and the whole xorg set of ports from scratch, but, as clearly stated here: http://people.debian.org/~terpstra/message/20061127.041128.8a08d75f.en.html some did not, due to code that is not compliant with libx11 and xcb APIs, whose checks are becoming stricter. So i could work around some of these problems (like OpenOffice that was relying on mesa3d built on older libxcb), but i couldn't find a way to get qt4 (taken from Sepen's repo) workig and i had to patch libxcb itself... i used this patch (yes i know it's a "regression" patch...): http://developer.momonga-linux.org/viewvc/trunk/pkgs/libxcb/libxcb-0.9.93-xc... and now qt4 are working plus i feel some (mainly gtk2-based) apps are much stabler, and don't randomly crash... I believe patching of libxcb for at least some months should be considered, as there is still lots of code around that won't work at all (like qt4) or worst, that will randomly close the app while working. bye, g -- NullPointer || GnuPG/PGP Key-Id: 0x343B22E6