who tagged this as resolved? because it's not, this bug is still affecting from 1.5.2 backwards, i ran, 1.6.1 and 1.5.1 and both 1.5.2 and 1.5.1 shows this error message.
Fernando Guillermo Obispo
who tagged this as resolved? because it's not, this bug is still affecting from 1.5.2 backwards, i ran, 1.6.1 and 1.5.1 and both 1.5.2 and 1.5.1 shows this error message.