I have had this problem for a long time, but it recently got fixed automatically during a dist-upgrade. It may have been the move to 3.3.12, but I am not sure. Can the reporters maybe check if they can still reproduce the bug with an up-to-date installation?
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
