I noticed this as well. It looks like 1.6.9p10-1ubuntu3.2 reintroduced this problem, at least on 32-bit. I didn't get to do much testing on it but I did notice that it had returned. I can provide more details when I get the chance to test but I'd say this problem is no longer fixed.

I noticed this as well. It looks like 1.6.9p10-1ubuntu3.2 reintroduced this problem, at least on 32-bit. I didn't get to do much testing on it but I did notice that it had returned. I can provide more details when I get the chance to test but I'd say this problem is no longer fixed.