Comment 49 for bug 176090

I know, I just didn't see any comments about it even being addressed upstream, or about a fix being available, a patch somewhere, or anything that could be tested.