Why no activity on this (nasty X segfault) bug?

[Simon Thum]

Hi Ian,

you seem not to be used to mailing lists. You should cc all the people
you want to read this mail, i.e. normally everyone already in to or cc
[0]. People read their email, but not the list archive. I did that as I
was interested in the progress on this issue.

I'm just stepping in since I'm affected as well and seemingly there
isn't much missing except for keith to take note of the results you
posted, which should be much more likely now.

@Keith: Please see below.

Cheers,

Simon


[0] If you bcc'ed people, please just ignore this.


On 04/27/2011 11:36 PM, Ian Pilcher wrote:
> On 04/27/2011 10:12 AM, Ian Pilcher wrote:
>> On 04/27/2011 10:00 AM, Mario Kleiner wrote:
>>>
>>> Original thread was this, between Michel and Keith:
>>>
>>> <http://lists.x.org/archives/xorg-devel/2011-March/020716.html>
>>>
>>> The refined patch of Keith that needs testing:
>>>
>>> <http://www.mail-archive.com/xorg-devel@lists.x.org/msg20650.html>
>>>
> 
> OK, I have rebuilt the latest Fedora 15 xorg-x11-server SRPM with
> Michel's "always regenerate front buffer information when asked for it"
> patch from 25 March and Keith's "invalidate DRI2 buffers for all windows
> with the same pixmap on swap" patch from 6 April.
> 
> Tested on my current system with Intel Core i7 2600 (HD 2000) graphics
> and my old system with an ATI X1650 PRO adapter.  On both systems, the
> two patches eliminate problems with corruption of the KDE screensaver
> unlock dialog (seen when KWin compositing and an OpenGL screensaver are
> used).
> 
> The problems that were foreshadowed by the dialog corruption were also
> eliminated -- X segfault on the Intel system and a nasty "flickering"
> effect that made X unusable on the ATI system.
> 
> If there is anything else that you'd like me to test before applying
> these patches, please let me know.
> 
> Thanks!
>