Comment 5 for bug 328671

It seems to have 'gone-away' - probably a result of one of the countless updates over the intervening period. I'll keep an eye on it and update status here once we get into April so the report can be voided if the issue no longer occurs.