Comment 29 for bug 441653

BTW, the fix for Bug #544590 seems to have fixed this issue for me, too.