It was fixed back when it first happened. I haven't seen anyone else with problems with it. Maybe it was an isolated incident?