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.
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.