[10:10] what is the purpose of the driver package kbd, evdev, mousedev are these part of kernel or x? [19:08] anyone know how to fix all these undocumented parameter warnings in libxcb's tests? http://sarvatt.com/downloads/libxcb_1.6%2bgit20100703.75ff427d-0ubuntu0sarvatt2_i386.build [19:16] i guess its a doxygen problem, WARN_IF_UNDOCUMENTED = NO is set in xcb.doxygen.in and isn't getting honored === Sarvatt_ is now known as Sarvatt [22:08] hope i can get away only updating libxcb and xcb-proto, xcb-util has a few soname bumps and i dont fancy breaking the things depending on libxcb-icccm1 and libxcb-event1 [22:09] someone emailed me saying libxcb needed updating past 1.6 because it was breaking things with the newer libx11 in xorg-edgers [22:11] isn't libX11 1.3.4 in debian too? http://cgit.freedesktop.org/xcb/libxcb/commit/?id=b0525e242368fffbc77ebb45293f34e80847e65a is apparently needed with it [22:12] no, still 1.3.3 [22:19] ah not released yet, thought i saw it merged on debian-x [22:24] I'm just a user running into a nasty bug: libxcb 1.6's release doesn't have necessary updates (already in git) vs. libX11 1.3.4. The result is (at times) low performance, with the ability for various apps (including compiz) to completely stop responding. How to trigger it, and what it does, are extremely inconsistent even just over time because the code is made racy. compiz and dolphin-emu (from another PPA) are both keen on triggering this bug, [22:24] but other compositing window managers (such as kwin and mutter) can also experience (on my machine) up to a 40% drop in performance, when they don't hang. [22:27] and hesays that libxcb commit fixes it as does downgrading to libx11 1.3.3