We had been anticipating a fix for this issue in time for intrepid from
libxcb upstream, but none was forthcoming. We did not have time during
intrepid to explore the option of de-enabling xcb in libx11 (it would
require changes to compiz and other things that now require it).
This bug has gotten long and difficult to follow, but we finally have
some hard data in comments #169, #171, #181 on the remaining issues. It
will require some additional analysis to determine if these bugs can be
individually addressed or would only be fixed by a libxcb revert. I'll
leave this bug open (but the intrepid task closed) in case of the
latter, but if the former looks realistic we should break those bugs out
into separate bugs so we can close this one.
** Changed in: libxcb (Ubuntu Intrepid)
Status: Triaged => Won't Fix
** Changed in: pygtk (Ubuntu Intrepid)
Status: Incomplete => Invalid
** Changed in: pygtk (Ubuntu Gutsy)
Status: New => Invalid
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
