Re: Faidon Liambotis > It turned out that for me, the cause was a disparity between libx11-xcb1 > and libx11-6 -- the former was at 2:1.7.0-1, while the latter was at > 2:1.6.12-1 (don't ask why...).
I had the same here on testing+unstable (the latter on lower pin priority), and upgrading libx11-6 fixed the problem. chromium depends on libx11-6 (>= 2:1.4.99.1), libx11-xcb1 (>= 2:1.7.0) which explains why only libx11-xcb1 got pulled from unstable. Christoph
