Comment 398 for bug 359392

I am aware of that. In what capacity I can, I apologize to Martin and you; I had exams that morning and was not in any sort of positive mood this morning. That being said, I will not - nor will I ever, personally speaking - accept being talked at like I am a half-wit; I can only assume that neither of you would, either, in any situation where your experience (or lack thereof) is not (or is, respectively) easily impressed on others.

> I suspect whatever issue you have is unrelated..

At this point, I highly doubt that considering that everything worked fine in Intrepid and rolling back to that driver fixed things to an extent. I am having the same class of bug, and have reported my personal version in bug 345119; this bug got virtually no attention and I was told by a handful of commenters to look here for more details.

I would, honestly, be astounded if anybody marked this bug as fixed (which it's on its way to) with the silly Virtual workaround fix, particularly with many users in the comments immediately after it voicing that it is not fixing their issues. This bug is about X freezes starting on April 3rd on the i965 chipset, is it not? Where else do you expect me to go here to fix this bug?