Comment # 37 on bug 1137373 from 
Sorry, this workaround was for a different case, where this problem occurred.

You are receiving this mail because: