Comment 3 for bug 247758

I don't find the number either know but I'm pretty sure it has been mentioned before in other bug, upstream might have decided to work on that and close the bug though