Comment 1 for bug 535149

Hmm, that is definitely something I have not seen before. Is there nothing else before that error in the terminal output? I'll try to reproduce this locally, in the meantime (probably not today, though)