Comment # 4 on bug 91193 from 
Seems to solve it for me also.
I'm guessing that this is just a temporary workaround?

You are receiving this mail because: