Comment 1 for bug 535716

Also seeing this problem since this morning (incidentally, this coincided with the start of the behaviour I described in bug #583214, don't know if the two could be related, though it seems somewhat unlikely).