The old bug discussion:
This issue seems to be present in 5.6 now. The issue was originally solved in 5.4b23, but the changelog for that version does not specificy any graphics backend changes that I think could have been the thing that fixed it, other than possibly: