Certain applications like gvim perform very slow rendering with certain fonts like Fixed (as of gvim naming). As far as I can see "Fixed" is not a ttf font (seems to be loaded from /usr/share/fonts/misc/6x12-ISO8859-1.pcf.gz file that belongs to xorg-fonts-misc package). Screencast: http://youtu.be/OnNNpOQrx18 Downgrading to 1.10.2 fixes the issue. A similar bug exists in the database: https://bugs.freedesktop.org/show_bug.cgi?id=48395 but that's for nvidia cards while I have an intel card. System info: $ uname -a Linux eartheart 3.4.2-2-ARCH #1 SMP PREEMPT Mon Jun 11 22:27:17 CEST 2012 x86_64 GNU/Linux $ lspci | grep -i graph 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) $ grep -i chipset /var/log/Xorg.0.log [ 35.233] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, [ 35.244] (II) intel(0): Integrated Graphics Chipset: Intel(R) Arrandale [ 35.244] (--) intel(0): Chipset: "Arrandale" $ pacman -Q | egrep 'cairo|intel' cairo 1.12.2-2 cairo-perl 1.082-2 cairomm 1.10.0-2 haskell-cairo 0.12.3.1-1 intel-dri 8.0.3-3 lib32-cairo 1.12.2-1 libva-driver-intel 1.0.18-1 python2-cairo 1.10.0-1 xf86-video-intel 2.19.0-3
T'is a driver bug, either use the much, much faster SNA acceleration method or apply commit 0a43d425670b883b04565296c0510e7ba03ba6de Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Jun 19 14:46:58 2012 +0100 uxa: Implement glyphs-to-dst to avoid fallbacks An earlier version was buggy and introduced corruption as it failed to fallback gracefully with ComponentAlpha glpyhs. This is a much simpler implementation that composites each glyph individually, leaving it to the backend to optimise away state changes. It should still be many times faster than incurring the fallback... Reported-by: Oleksandr Natalenko <pfactum@gmail.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=50508 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> *** This bug has been marked as a duplicate of bug 50508 ***
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.