I'm marking the libxcb bug won't fix for hardy because a) the only
libxcb "fix" we can deploy at this point would be to disable libxcb
entirely - with the side effect of disabling compiz for everyone (c.f.
comment #137), and b) a viable workaround exists (c.f. comment #144).
See bug #236676 for details.
Leaving it open for Intrepid, as we expect to see a new libX11/libxcb
with the relevant fixes within a month or so.
** Changed in: libxcb (Ubuntu Hardy)
Status: Confirmed => Won't Fix
** Changed in: libxcb (Ubuntu Gutsy)
Status: New => Invalid
** Changed in: openoffice.org (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
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
