It also appears that this has been a known bug for at least 3 weeks with no resolution. This is simply not acceptable.
