Comment # 5 on bug 1017824 from Jiri Slaby

And it is possible that the 1.1.2->1.1.3 update fixed it. I could not reproduce
after the latest update so far.