Comment 14 for bug 545201

I didn't know that limiting who could run apport-collect on a bug report had been turned on, but in general it is a good thing, since we often get "apport-collect-bombed" with information that we do not need. Hardly ever would we want someone who is not the original reporter of a bug to run apport-collect to that bug. For a duplicate bug, I'm not so sure, but it is easy to work around by unduplicating the bug temporarily, running apport-collect and then duplicating the bug. The advantage of this is that the other people subscribed to the bug master bug report don't get 20+ mails. Of course, the real problem here is that apport-collect triggers one comment per attachment.

Anyway, in this particular case, I don't think apport-collect will upload the particular dumps that are useful, so you don't have to run it.

In the long term, we want to use KMS and framebuffer compression. But since the Lucid release date is getting close we want to identify workarounds that may make the systems usable until the real bug is fixed. This is why we would like feedback on whether turning KMS off helps, and how much it helps. From the comments upstream it is clear that the bug is not is in the KMS specific code, but that some parts of the driver is much faster with KMS and that the bug therefore may be triggered much more easily with KMS that UMS. In order to decide what our best option is, we need feedback from affected users to know if there is a real improvement.

It looks like framebuffer compression is not supported anyway on 855GM, so disabling it should have no effect. It has recently been disabled on 915GM and 945GM since there were problems with it there. This kind of features can be found in i915_drv.c in the kernel driver [1]. Look for the string "has_fbc".

[1]: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/gpu/drm/i915;h=7de084e6751446b405dda1b2a2e0406b366222cb;hb=5e11611a5d22252f3f9c169a3c9377eac0c32033