Comment 76 for bug 753971

Sam, that's all well and good (and an inherent part of software development...), however; If you folks feel the need to close the bug for internal bookkeeping / organization / spring cleaning / warm fuzzies / whatever-you-want, then it would be damned spiffy if you could also take a moment to spin off some other bugs for the similar issues that are reported here that have not been fixed.

It's sure not clear to me that the issues I'm having are unrelated to the screen corruption problems that have been reported as fixed, so if I go create a bug it's likely to be closed as a duplicate of this one, since I don't know how my problems are different.