Created attachment 31801 [details] Screenshot of the 2 extra black blocks System Environment: -------------------------- Arch: x86-64 Platform: G45 Mesa: (master)07487643515edb731c6abc3e931c329a89dd9293 Xserver: (master)fd867387335b6175d76bbe93118bbe5e1e45ce88 Xf86_video_intel: (master)415aab474edd1425034981306718afd8506445f1 Libdrm: (master) 9707733a130098a7d9959e72ebd782d8119a23d3 Kernel: (master)22763c5cf3690a681551162c15d34d935308c8d7 Bug detailed description: ------------------------- The desktop is gnome. With compiz enabled, the cursor format and cursor blink rate in console is wrong. For example, typing a character in console gets 2 extra black blocks(can be seen on the screenshot), or the cursor is always blink. It works fine if disabled compiz. This issue happens after the Bug 25409 was fixed. Following is the bug report: http://bugs.freedesktop.org/show_bug.cgi?id=25409 Reproduce steps: ---------------- 1.start gnome 2.open a terminal 3.typing any character
Created attachment 31802 [details] Xorg log
commit cd475bad23c02130d11c49882c11261c9f0d4ef1 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Dec 7 11:09:14 2009 +0000 batch: Ensure we send a MI_FLUSH in the block handler for TFP This should restore the previous level of synchronisation between textures and pixmaps, but *does not* guarantee that a texture will be flushed before use. tfp should be fixed so that the ddx can submit the batch if required to flush the pixmap. A side-effect of this patch is to rename intel_batch_flush() to intel_batch_submit() to reduce the confusion of executing a batch buffer with that of emitting a MI_FLUSH. Should fix the remaining rendering corruption involving tfp [inc compiz]: Bug 25431 [i915 bisected] piglit/texturing_tfp regressed http://bugs.freedesktop.org/show_bug.cgi?id=25431 Bug 25481 Wrong cursor format and cursor blink rate with compiz enabled http://bugs.freedesktop.org/show_bug.cgi?id=25481
It works well. I verify it.
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.