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?
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
