> I've just downgraded to 3.2.1-1 from testing, and it has the same > problem. I suppose that means that the problem is in a different > package. How should I go about finding it?
I've got the same problem on debian testing (awesome 3.2.1-1) right after upgrading libxcb1 from 1.2-1 to 1.3-2. Downgrading libxcb1 back to 1.2-1 solves the problem. Please confirm if this also applies to your case. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
