And the bug was not addressed in Patch 2.25, so I'm beginning to doubt that the report being moved to the Resolved thread indicates that the problem has been addressed.