Comment 113 for bug 1164016

> If that is genuinely the reason (and this bug has been marked as "Fix Released"
> since Jan 2014, so it seems correct), then is it not time to raise a new bug?

Maybe (though it seems a little stupid to raise a new bug for exactly the same issue).

Anyway I did, like yesterday, and it got closed
(can't find it right now, I don't know what's wrong with the search engine of this stupid bug tracker)