To be honest, I had hoped that this would have proven to be the
unfenced-BLT bug. The known w/a for UXA is to enable DebugWait, which
implies that UXA is not handling its domains correctly.
The most likely candidate is:
diff --git a/src/intel_uxa.c b/src/intel_uxa.c
index 76a3146..40e3b67 100644
--- a/src/intel_uxa.c
+++ b/src/intel_uxa.c
@@ -1379,8 +1379,8 @@ Bool intel_uxa_init(ScreenPtr screen)
}
/* PutImage */
- intel->uxa_driver->put_image = intel_uxa_put_image;
- intel->uxa_driver->get_image = intel_uxa_get_image;
+ //intel->uxa_driver->put_image = intel_uxa_put_image;
+ //intel->uxa_driver->get_image = intel_uxa_get_image;
intel->uxa_driver->prepare_access = intel_uxa_prepare_access;
intel->uxa_driver->finish_access = intel_uxa_finish_access;
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745608
Title:
[915GM] font corruption on Intel GMA900
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/745608/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
