The issue seems back, cf. bug #1004686. (But I'm keeping this closed, since it may be a different root cause.)