Dang, is compiz the only major application that needs both X11 and xcb? Because if it is, wouldn't it make more sense to link compiz against "libX11-xcb.so" and leave "libX11.so" be the non-xcb, stock/old/stable/working libX11?
I suggest this, as I hope you guys rethink the magnatude of the wontfix status. Hardy essentially doesn't work out of the box with all Java applications and countless other closed & open, current & old applications. I think this is especially important as Hardy is supposed to be a LTS/stable release, that one can count on for larger, more long term deployments (such as one I'm trying to do, but this bug is holding up).
Dang, is compiz the only major application that needs both X11 and xcb? Because if it is, wouldn't it make more sense to link compiz against "libX11-xcb.so" and leave "libX11.so" be the non-xcb, stock/old/ stable/ working libX11?
I suggest this, as I hope you guys rethink the magnatude of the wontfix status. Hardy essentially doesn't work out of the box with all Java applications and countless other closed & open, current & old applications. I think this is especially important as Hardy is supposed to be a LTS/stable release, that one can count on for larger, more long term deployments (such as one I'm trying to do, but this bug is holding up).
Thanks for your consideration.