according to the debian bug report this issue was fixed in 1:3.2.7-4 - so fixed in hardy (1:3.2.7-5ubuntu1) -> fix released for ubuntu ?
according to the debian bug report this issue was fixed in 1:3.2.7-4 - so fixed in hardy (1:3.2.7-5ubuntu1) -> fix released for ubuntu ?