Also see bug #740342, I was unsure if perhaps some bits hadn't fully upgraded, but looks like he did another update to latest and it occurred again.
Also see bug #740342, I was unsure if perhaps some bits hadn't fully upgraded, but looks like he did another update to latest and it occurred again.