I'm encountering this same issue only after having just upgraded to 1.5.5e...