[Xcb] Bug#401571: xcb_xlib_lock assertion happens on gvim, too

Julien Cristau jcristau at debian.org
Tue Feb 20 23:28:41 PST 2007

On Wed, Feb 21, 2007 at 00:55:22 +0000, Brian M. Carlson wrote:

> I have experienced a similar assertion:
> gvim: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
> Vim: Caught deadly signal ABRT
> I don't know exactly when it happened, but it did not interfere with my
> editing; it appears to have happened sometime after I was done with what
> I was doing, potentially when the screensaver was on.  Sorry I couldn't
> be more specific, but I wanted to point out a similar occurrence.
> If there is anything you need me to do to test, please let me know.
Hi Brian,
please read this message:

This message represents a bug in a caller of libX11, so if you can
reproduce this assertion, please try to get a backtrace with gdb and see
which library/application is calling XLockDisplay()/XUnlockDisplay(),
this will tell you where the bug is.


More information about the Xcb mailing list