On 11/12/07, Kow <[EMAIL PROTECTED]> wrote: > If I reapply the "allow sloppy locks" workaround patch to libxcb the > problem is gone.
By "the problem", you mean the stack trace you just reported? That's very strange. I can't find anything related to Xlib or XCB near the top of the stack traces you provided, though the memory map confirms that you are using XCB. A variant of the "allow sloppy locks" patch has been committed upstream in XCB and is in the recent 1.1 release, so hopefully it will make it into Ubuntu in the near future. I dunno, maybe they're waiting for me to roll a new Debian package, which I haven't had time to do yet. :-/ -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/86103 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
