Comment 5 for bug 1335478

Kit Davis (kdavis-j) wrote :

it seems that in the 12.04 stream, the error is no longer present in 3.2.0.67