Comment 20 for bug 122389

Well, considering I wasn't able to describe how to reproduce the bug in the original report, and noting that the original report was almost five years ago, I could not possibly even begin to confirm the continued existence of the bug right now. You may as well close this report, unless anyone else cares to try. Thanks for the response, though: considering the last activity was three years late, being only two years late is a substantial improvement!