If I reapply the "allow sloppy locks" workaround patch to libxcb the problem is gone. I'm guessing this was removed because the thought was this was fixed upstream?
If I reapply the "allow sloppy locks" workaround patch to libxcb the problem is gone. I'm guessing this was removed because the thought was this was fixed upstream?