This bug is fixed by Martin Landa in 6.3 and 6.2 CVS. I was wondering - could the vector cleaning that v.in.ogr performs suffer from this bug too? Or does v.in.ogr use the same code that v.clean does, so that a fix for v.clean fixes the problem for v.in.ogr too? Maciek