Created attachment 106748 [details] Test application Since several years MSEgui doesn't work with radeon driver anymore. http://sourceforge.net/projects/mseide-msegui/ https://bugs.launchpad.net/ubuntu/+bug/373781 https://bugzilla.novell.com/show_bug.cgi?id=690766 https://bugzilla.novell.com/show_bug.cgi?id=852944 https://bugs.freedesktop.org/show_bug.cgi?id=69543 I again unsuccessfully spent several days to try to find a bug in MSEgui, try to find a workaround or to find a small testapplication which shows the problems. MSEgui paints on a pixmap with the size of the update region which is moved to the window by xcopyarea() after the drawing is complete. The attached application draws a diagonal line over a grid cell. Every 2 seconds the cell will be invalidated and refreshed. At startup the display is OK, after 2 seconds the diagonal line will be truncated. This has been reproduced on three installations. If the test-program is started with any command line parameter (ex. "./radeonline abc" the drawing of the blue rectangle is disabled. Two of the three installations always show the diagonal line in this mode with full length, one truncates it after 2 seconds. With the option "EXAPixmaps" "off" in xorg.conf all is OK. The simplified testprogram from https://bugs.freedesktop.org/show_bug.cgi?id=69543 shows a distorted display also by directly drawing to the window so the double buffering probably is not the culprit.
Probably an EXA issue. Option "EXAPixmaps" "off" mostly avoids the hardware acceleration paths in EXA.
Who is responsible for "Server/Acceleration/EXA"?
Nobody has actively worked on EXA for years.
What to do now? What do you recommend?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/82.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.