known, and has been fixed recently (to be honest this bug is there since the first release of 0.72 and we forgot to fix it in every subsequent release, but in the next this error will be gone for sure).