It's seems that the workaround #1 works for some people (says arch forums and etc)
Information on libxcb The libxcb developers have decided to be strict in asserting locking bugs in X11 applications. This is different than the behavior of libX11 when used on its own, and it will cause some applications to crash when they previously did not. When an application has these types of bugs, it will crash with the following assertion: xcb_xlib_lock: Assertion `!c->xlib.lock' failed. The patch applied above to libxcb adds an environment variable, LIBXCB_ALLOW_SLOPPY_LOCK, to be set which will allow the locking bugs to not crash the application. It is a workaround that is known to be needed in a few cases. If it is found that these bugs affect an application in use, add the following to your system or personal profile: export LIBXCB_ALLOW_SLOPPY_LOCK=1 -- azureus crashes on hardy https://bugs.launchpad.net/bugs/161108 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
