Timo, please revert to sloppy locking and let that be the end of it. The current situation makes no sense at all: Having applications crash because of a _recoverable_ error is just stupid. It seems like an extremely dickish move by the xcb developers (or whoever is responsible for this insanity) to punish end users in order to prove a point to application developers (who, in the case of java, evidently don't even give a shit), especially since they couldn't even be bothered to include a clear warning in their debug messages that this type of leniency was likely to be removed in a later version of the lib. (Of course, even that wouldn't have prevented "masked" bugs of this type, the correct way to change their locking semantics would have been to introduce a new locking mechanism and deprecate the old one, giving developers a chance to fix their programs and not leaving end users baffled as to why their apps keep crashing)
No adverse effects are to be expected from this change since (a) sloppy locking does not change the behavior of applications and (b) those applications that work with sloppy locking are a strict superset of those that work without. This is not an issue anybody's time should be wasted on. -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
