Comment 21 for bug 398244

Hi Bryce,

I have to agree that it's hard to prioritize this bug over things that cause lockups of the GPU or failure to login. But at the same time, I do have a part of me that is anxious to make every last pixel correct. :-)

Jaime,

I think what we'll need next is a smaller test case to help us know exactly what operation is resulting in the missing pixel. It's a bit too much for us as driver hackers to hear "wine dialog" and know what the problem might be. Could you perhaps do some investigation to find out as much as you can about what is actually being drawn here? Is it lines? Filled rectangles? Outlined rectangles? And how it's being drawn: Is wine using XDrawLines? XDrawRectangle? cairo calls?

Ideally we could get this down to a single call, (say one XDrawLines request), where the vesa driver and the intel driver behave differently. If we had that, I would guess that it should be quite easy to identify and fix the bug.

One very good approach to getting this information might be to run an X protocol capture tool and capture a trace. For example:

    xtrace &
    DISPLAY=:9 wine ./whatever/program/shows/the/bug

There will be a lot of output, (but the more simple program you can use, the better of course). But hopefully by knowing where on the screen the missing pixel is, you can grep through the trace and find where the problem is.

Oh, another thing you might try is to instead run "xtrace -i" in a separate terminal rather than running it in the background. This puts xtrace into an "interactive" mode where you have to press Enter before it forwards each request. This way you can control how slowly the application runs and know when the right range of output is appearing in the protocol trace.

I hope that helps and that we can track down your missing pixel for you.

-Carl