After I upgrade to gtk+ 2.8.x, the fonts get corrupted in some applications. Most notably in gvim and in gimp's menus. I'm attaching a screenshot of gvim. The same corruption occurs in the menus and in the gimp menus and dialogs. It's also worth noting that by moving another window over the window clears up the fonts, as does highlighting the menu items. Downgrading to 2.6.x fixes the problem. This issue has also been mentioned on usenet at http://groups.google.ca/group/linux.gentoo.user/browse_thread/thread/15019e5acb611797/0cfaa53905598571 Reproducible: Always Steps to Reproduce: 1. Launch gvim or gimp Actual Results: Corrupted fonts Expected Results: Clear fonts Portage 2.0.53_rc7 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r3, 2.6.14 x86_64) ================================================================= System uname: 2.6.14 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.12.0_pre10 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.13 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=athlon64" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.cs.mun.ca/pub/mirror/gentoo/ http://mirrors.tds.net/gentoo ftp://mirrors.tds.net/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage" USE="amd64 X X509 aac alsa amd arts audiofile avi berkdb bitmap-fonts bzip2 cddb cdparanoia cdr crypt cups curl dvd dvdr eds emboss emul-linux-x86 encode esd exif expat fam ffmpeg flac foomaticdb fortran gcj gd gdbm gif gimp glut gmp gnome gphoto2 gpm gstreamer gtk gtk2 guile idn imagemagick imlib innodb ipv6 java jpeg junit kde lcms ldap libwww lirc lm_sensors lzw lzw-tiff mad mikmod mng mozcalendar mozilla mp3 mpeg musicbrainz mysql ncurses nls noxalan nptl offensive ogg opengl pam pcre pda pdf pdfkit pdflib perl png python qt quicktime rdesktop readline samba sdl spell ssl tcltk tcpd tetex tidy tiff timidity transcode truetype truetype-fonts type1-fonts udev unicode usb userlocales vorbis wxgtk1 xine xml xml2 xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
Created attachment 73273 [details] Screenshot
Hi, we are talking about GTK+ 2.8.7, right? If no, have also tried the last version into the portage tree?
(In reply to comment #2) > Hi, we are talking about GTK+ 2.8.7, right? If no, have also tried the last > version into the portage tree? I've seen it on both gtk+-2.8.6 and gtk+-2.8.7
What else are you running? I only get this when I have a full-screen Xv app (such as mplayer) running, and switch desktops. And, even then, only on modular X. Do you have composite running (I do)? When I exit the Xv app, the problem goes away entirely.
(In reply to comment #4) > What else are you running? I only get this when I have a full-screen Xv app > (such as mplayer) running, and switch desktops. And, even then, only on modular > X. Do you have composite running (I do)? > > When I exit the Xv app, the problem goes away entirely. I do have Composite enabled, but I'm not running any Xv apps. It might also be worth mentioning that I'm running KDE, not GNOME.
I'm experiencing the same corruption, and so do many others: http://forums.gentoo.org/viewtopic-t-393284-highlight-gtk+fonts.html http://forums.gentoo.org/viewtopic-t-393804-start-0-postdays-0-postorder-asc-highlight-.html I'm running KDE and GTK+ 2.8.7, although I experienced the same problem with GTK+ 2.8.6. Someone suggested disabling the XRENDER acceleration provided by the nVidia binary drivers, but I'm actually using the nv drivers.
Addendum: I am not using the Composite extension. X.org X11 6.8.2-r6.
I'm having the same problem as well, more annoying is that fact that firefox 1.5 requires gtk+ 2.8.7 when its emerged. Is this only happening for ppl running gtk apps from with in kde?
Bug persists with GTK+ 2.8.8.
could those reporting this problem state the versions of their freetype, Xorg & pango installs. Also mention if you have composite loaded in your xorg config (isn't the same thing as using it).
Package versions: media-libs/freetype: 2.1.10 x11-base/xorg-x11: 6.8.2-r6 x11-libs/pango: 1.10.1 X11: - No composite extension loaded. - Using the 'nv' driver. Notes: - revdep-rebuild and emerge --newuse have nothing to do; everything is up to date. - CFLAGS: -O2 -march=athlon-xp -pipe.
Package versions: [ebuild R ] media-libs/freetype-2.1.9-r1 -bindist -doc +zlib 0 kB [ebuild R ] x11-base/xorg-x11-6.8.2-r6 -3dfx -3dnow +bitmap-fonts -cjk -debug -dlloader -dmx -doc +font-server -insecure-drivers -ipv6 -minimal +mmx +nls -nocxx +opengl +pam -sdk +sse -static +truetype-fonts +type1-fonts (-uclibc) -xprint +xv 0 kB [ebuild R ] x11-libs/pango-1.10.1 -debug -doc 0 kB X11: no composite enabled Option "RenderAccel" "True" <-- changing this to false fixes my problem, but as i understand shouldn't have this effect i'm using nvidia drivers CFLAGS: "-march=pentium4 -Os -pipe -fomit-frame-pointer"
media-libs/freetype-2.1.9-r1 -bindist -doc +zlib x11-libs/pango-1.10.1 -debug -doc x11-base/xorg-x11-7.0.0_rc2-r1 -xprint Composite enabled and in use RenderAccel set to True Using nvidia driver: media-video/nvidia-kernel-1.0.7676-r1
No change with pango 1.10.2 and gtk+ 2.8.9 (using the 2.8.8 ebuild with a changed version number).
Are you all on amd64? All of you have a Nvidia video card? All of you have Option "RenderAccel" "True"?
(In reply to comment #15) > Are you all on amd64? > All of you have a Nvidia video card? > All of you have Option "RenderAccel" "True"? I'm all of those things.
*** Bug 115341 has been marked as a duplicate of this bug. ***
I'm using IA32 and nvidia card with proprietary drivers. The problem does go away when I set RenderAccel to false.
> Are you all on amd64? No, Athlon XP -> IA-32. > All of you have a Nvidia video card? nVidia GeForce 6800 Ultra. > All of you have Option "RenderAccel" "True"? No, since the open source "nv" driver does not recognize that option.
Same problem here with apps like Firefox and Azureus. Xorg 6.8.2-r6 FreeType 2.1.10 Pango 1.10.2 nvidia-kernel 1.0.8174-r1 RenderAccel enabled Composite disabled This is on AMD Athlon 64 machine - 64 bit mode.
here is the upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=313646
Not quite the same bug (as reported upstream) as I have antialiasing on in firefox and it still does it. > Are you all on amd64? No - Pentium 4 > All of you have a Nvidia video card? nvidia 6800GT > All of you have Option "RenderAccel" "True"? I have it set to true - using lastest nvidia drivers (1.0.8174-r1)
The upstream bug has boiled down to broken binary nvidia drivers with RenderAccel set to true, if I read it correctly.
Well if you look at the forum posts listed above then you'll see at least one user who is running the nv driver and still has the problem.
Actually, I was mistaken - I do in fact use the nVidia binary driver with RenderAccel enabled. Disabling it solves the problem. To explain how I made this mistake: The GTK+ apps that exhibited the broken font rendering are actually running on a remote machine, which I control from afar using the terminal server technology NX (www.nomachine.com). Now, the X server on that remote box does use the "nv" driver, however unlike VNC which essentially transmits screen captures of the remote desktop, NX transmits X11 protocol primitives (as I know only now). The local client application is an X server instance running in some kind of Xnest-like setup - and my local X server uses the "nvidia" driver. We've nailed the issue, then.
OK so the problem is related to : * NVidia card * NVidia driver (Sure with 1.0.7676-r1 and 1.0.8174-r1 versions) * Option "RenderAccel" "True"
*** Bug 114644 has been marked as a duplicate of this bug. ***
In this web forum thread, an nVidia engineer has responded to a description of the problem: http://www.nvnews.net/vbulletin/showthread.php?t=61763 Full quote: "There are currently known issues with RenderAccel. We hope to address most, if not all of the known issues in the first driver release of 2006. Thanks, Lonni"
NVidia driver 1.0.8178 was released and are in the portage tree. Here the bug #116400 for the bump, in the changelog there is this entry "Fixed a corruption bug with RenderAccel and the Composite X extension when using wide desktops." ... Is this problem? please try with this newer version and see if this bug is fixed. If yes ... probably GTK+ 2.8 can be marked stable...is this a christmas present ;)?
Nope, still broken here with the new NVidia drivers.
Nope, bug persists.
We can't fix bugs with binary drivers. GTK upstream won't deal with it either. Please contact nvidia for bugfixes.
Same problem here. Deactivating RenderAccel solved it.
This problem has disappeared for me after upgrading to the new nVidia driver version 1.0-8756: http://www.nvidia.com/object/linux_display_ia32_1.0-8756.html
I'm not sure wheter this bug is really solved upstream. I've got the same problems and I'm not using the binary drivers, removed them completely months ago. I'm using nv on AMD64 no composite or other X extensions. media-libs/freetype-2.1.10-r2 x11-base/xorg-x11-7.1 x11-libs/pango-1.12.3 x11-libs/gtk+-2.8.20-r1 If this is another kind of bug I'd like to know where to search for more information. For firefox export MOZ_DISABLE_PANGO=1 is an usable workaround but for other apps like Gimp it's really annoying.
For me: firefox (compiled) bad fonts at page area, firefox (bin) is like using MOZ_DISABLE_PANGO=1. I'm using fglrx, I've tried with RenderAccel true and false. I'm using x11-libs/gtk+-2.10.6, Thunderbird works fine, although firefox 2 is all messed up. I'm getting desperate! (In reply to comment #35) > I'm not sure wheter this bug is really solved upstream. I've got the same > problems and I'm not using the binary drivers, removed them completely months > ago. I'm using nv on AMD64 no composite or other X extensions. > media-libs/freetype-2.1.10-r2 > x11-base/xorg-x11-7.1 > x11-libs/pango-1.12.3 > x11-libs/gtk+-2.8.20-r1 > > If this is another kind of bug I'd like to know where to search for more > information. For firefox export MOZ_DISABLE_PANGO=1 is an usable workaround but > for other apps like Gimp it's really annoying. >
