Since we got the fix for this bug in Precise through upstream 3.2 stable, I am tagging this bug as verified in Precise as well.
Since we got the fix for this bug in Precise through upstream 3.2 stable, I am tagging this bug as verified in Precise as well.