not sure why this bug had been reopened but if you have a similar issue in recent versions open a new bug rather, the code changed in those years and the issue is a different one now
not sure why this bug had been reopened but if you have a similar issue in recent versions open a new bug rather, the code changed in those years and the issue is a different one now