This bug still exists in 2.8.17, and is still a serious problem. I investigated further and, at least in my case, this only shows up with a remote X server. Perhaps that explains why more people haven't noticed the problem.