*** This bug is a duplicate of bug 87947 ***
https://bugs.launchpad.net/bugs/87947
This happened for me running a custom Eclipse Plug-in. The issue was
referenced in some other locations as having been a problem in the past.
This issue happened to me on Hardy, but I had not seen it on Gutsy.
*** This bug is a duplicate of bug 87947 ***
https://bugs.launchpad.net/bugs/87947
** This bug has been marked a duplicate of bug 87947
xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
--
c->xlib.lock failed
https://bugs.launchpad.net/bugs/187421
You received this bug noti
As postet on
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373
there is a workaround for java applications.
You have to set
$ export LIBXCB_ALLOW_SLOPPY_LOCK=1
before you can run java programs.
--
c->xlib.lock failed
https://bugs.launchpad.net/bugs/187421
You received this bug notificat
Also affects Limewire (output below):
Starting LimeWire...
Java exec found in PATH. Verifying...
Suitable java version found [java = 1.6.0_04]
Configuring environment...
Loading LimeWire:
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0xb542d767]
#1 /usr/lib/libxcb-xlib.so.0(
