This bug should have been fixed in development version from r489. Please, could you confirm that this error happens only on stable version (1.16)?
This bug should have been fixed in development version from r489.
Please, could you confirm that this error happens only on stable version (1.16)?