#4 - Oct. 13, 2010, 3:51 a.m.
Known issue, folks. Sorry for the inconvenience, but this is currently being looked into by our Quality Assurance team at this time. If I receive any information on it, I'll be sure to share it, but I currently do not have an ETA on the situation.