[i965] GM965/GL960 intel freeze with kde desktop effects

This bug report has been inactive for quite some time and in the meantime Ubuntu has moved along. I hope the reported problem has been resolved in the current version of Ubuntu. If it has not and there are people willing to follow up with information collecting and testing, it is best to file a new bug report with the latest Ubuntu development version (10.04 still works, but soon 10.10 is better), using the ubuntu-bug command if possible. Feel free to mention the bug number of this bug.

We are sorry that we are not always have the capacity to look at all reported bugs in a timely manner. Occasionally we have to purge old bug reports where no progress has been made, whether it is due to reporter not being able to respond or lack of manpower on the Ubuntu side, in order to keep our list of "active" bugs current. Sorry for the inconvenience this may cause.

Here are a few tips that will make it easier for triagers and developers to process your bug:
* Read https://wiki.ubuntu.com/X/Reporting
* Browse https://wiki.ubuntu.com/X and see if there is some relevant information for you problem
* Respond quickly to questions from triagers
* Try changing things to see if the behaviour changes, e.g.
  * A new mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D (more information at https://wiki.ubuntu.com/KernelTeam/MainlineBuilds)
  * The xorg-edgers PPA: https://launchpad.net/~xorg-edgers/+archive/ppa
  * Various options in `/etc/X11/xorg.conf` (see `man intel`)
* Browse other bug reports to see if you find a similar one and provide the information that is being asked for there.

What would you have liked to see or have me do to keep the bug report alive?
I did read the links before posting and added all the possible logs mentioned in X bug reporting to my initial message.

I would have liked to see a reply and am available for replies if questions are asked.

The bug is not relevant for me anymore, I have since switched to 64bit system. I would just like to know how to make a report that actually gets a reply.

regards myrtille

Most of all, I would have liked to see this bug report dead long ago.
But resolved, not closed because of age.

Ideally, you would have received a reply with request for a testcase
or two soon after you reported it, and we could have reported it
upstream. The point is, we're not blaming you for anything. The bug
has been reported well, and the only reason it wasn't followed up is
lack of manpower (in this case, I'm using this standard text for many
old bug reports).

While the attached information was relevant at that time, it no longer
is. One way of keeping the bug report alive would be to update it with
the same information for the newest Ubuntu (for this kind of bug we
would actually have needed it with newer mainline kernels). However,
at this point it is better with a new bug report, since we then
wouldn't need to carry all the now outdated stuff.

I'm surprised that switching from 32bit to 64bit made a difference.
For most bugs it doesn't matter.

PS: You may be able to help on the manpower problem by help triaging
similar bugs.