If people are seeing similar errors as the one reported by Simon, I think it's likely related to bug 455544 which has a workaround noted in the description.
If people are seeing similar errors as the one reported by Simon, I think it's likely related to bug 455544 which has a workaround noted in the description.