Version: (using KDE KDE 3.1) Installed from: Compiled From Sources Compiler: gcc 2.95.4 FreeBSD 4.x native compiler OS: FreeBSD I call your attention for an issue early described in old bug #18876. That problem happened to me - e.g. all fonts became look the same - after upgrading XFree86 from 4.2.1 to 4.3.0. Obviously, Xft version has been changed, that caused inconsistencies in Qt. I've rebuilt Qt (v3.1.2) after, but fonts all look the same except few like Courier. The xfontsel as well as xlsfonts shows all fonts well, so it's maybe Xft or Qt rejects fonts by some obscured reason which I can't understand. Any ideas and advices are much appreciated.
I've got a very similar problem. Many fonts are not working anymore after upgrading from XFree 4.2.1 to 4.3.0, they appear in the list, but, as you say, they all look the same.. However, my system is: Solaris 9 x86 XFree 4.3.0 GCC 2.95.3, GNU binutils 2.13.2.1 QT 3.1.2 KDE 3.1 I've noticed two more details: - if a fontpath is put in /etc/X11/XF86config, and not /etc/fonts/local.conf, the font appear in X apps (like xfontsel), but *not* in fontconfig apps like KDE. - displaying the font in KDE font installer works, but the font still doesn't work after it's installed.
Hi, I've got very same bug after running upgrade two days ago... All fonts look same except for msttcorefonts! Any ideas how to solve it? Thanks a lot!
Created attachment 1189 [details] Fonts bug after upgrade Take a look on my control center. Helvetica font appears same with all other fonts. Also, strangely, none of these same fonts is scalabale, they all appear as bitmap, even though that I set unscalable in XF86config.
Subject: Re: fonts all look the same Message of Victor Korobov at Mar 16 19:46 ... VK> ------- Additional Comments From victorio@onvol.net 2003-03-16 20:45 ------- VK> Created an attachment (id=1189) VK> --> (http://bugs.kde.org/attachment.cgi?id=1189&action=view) VK> Fonts bug after upgrade VK> VK> Take a look on my control center. VK> Helvetica font appears same with all other fonts. Also, strangely, none of VK> these same fonts is scalabale, they all appear as bitmap, even though that I VK> set unscalable in XF86config. After a short investigation I went out with the following thoughts: 1. It's obviously an Xft or fontconfig bug, neither Qt nor KDE which use fontconfig's output as is. 2. It touches only localized (cyrillic) fonts, not us-ascii ones. It's quite obvious on mixed language sites where us-ascii and cyrillic on the same line look very different. 3. XFree86 4.3.0 tries to use bundled the following libraries bundled: expat-1.95.2 Xft, both Xft1 and Xft2 fontconfig freetype which all exist in the newer and probably better version. Building X with those libraries installed manually requires a set of definitions in xc/config/cf/host.def and at least two hunks of patch for xc/config/cf/X11.tmpl. I've still incomplete my research about that so I can't provide full details now, but at least you'll need #define HasExpat YES #define HasFreetype2 YES #define Freetype2Dir /usr/local #define BuildXftLibrary NO #define BuildXft1Library NO #define UseFontconfig YES #define HasFontconfig YES #define PreloadXFTSetup LD_PRELOAD="`(cd $(XENVLIBDIR); echo libXft.so.? libXrender.so.? libfontconfig.so.?)`" in your xc/config/cf/host.def and apply the patch below. Another solution might be (just a suggestion, still untested, will try if nothing else helps) to rebuild Qt with -no-xft configure option. --- xc/config/cf/X11.tmpl.orig Tue Mar 4 18:21:10 2003 +++ xc/config/cf/X11.tmpl Mon Mar 17 12:08:40 2003 @@ -3028,8 +3035,11 @@ #endif /* else BuildFreetype2Library */ -#if BuildFreetype2Library || HasFreetype2 -FREETYPE2INCLUDES = -I$(FREETYPE2INCDIR) -I/usr/local/include +#if HasFreetype2 +FREETYPE2INCLUDES = -I$(FREETYPE2INCDIR) -I$(FREETYPE2INCDIR)/include +FREETYPE2DEFINES = -DFREETYPE2 +#elif BuildFreetype2Library +FREETYPE2INCLUDES = -I$(FREETYPE2INCDIR) FREETYPE2DEFINES = -DFREETYPE2 #endif @@ -3189,7 +3199,7 @@ #define XftClientLibs $(XFTLIB) FontconfigClientLibs $(XRENDERLIB) #endif -XFTINCLUDES=$(FONTCONFIGINCLUDES) $(FREETYPE2INCLUDES) +XFTINCLUDES=$(FONTCONFIGINCLUDES) $(FREETYPE2INCLUDES) $(LIBDIR) #if UseFontconfig SY, Seva Gluschenko, just stranger on The Road. Demos-Internet NOC | GVS-RIPE | GVS3-RIPN
This is not a kde bug (well, at least not only). I've got this problem too after upgrading to XFree86 4.3.0. The font shown is the same everywhere because kde uses a default one. Take a look to the file /etc/fonts/fonts.conf. Then run fc-cache. Maybe you will need to remove/rename the .kde dir in your home directory.
Well, nice advice. Just remove your ~/.kde and lose all your bookmarks made at Konqueror, at least. No, thanks. Of course, I've tried fresh version of fontconfig and rerun fc-cache blah blah blah all that stuff. No, sir, X rebuild is needed, as I see. Regarding to my previous comment, it DOES contain errors, because it's still work in progress. XFree86 can't be configured for your needs after a very first look, so I need more testing before actual patch will be posted. I'll place it as soon as I finish my test.
I've tried everything, even removed / re-installed font packages and xfstt... still same problem.
Well, after all it's the truly Qt/Fontconfig (Xft) interaction problem. The only solution (but what's the hell? It works!) I've found is to rebuild Qt with -no-xft option. I'm gonna to report it for Trolltech and I close this bug here since it's definitely not KDE's bug. If somebody's gonna find out the fix for Qt and notify me it would be appreciated much.
Qt heads told me they did not encounter this problem, but their extensive tests are still in progress. One Linux user solved the similar problem by simply removing ~/.fonts.cache-1, but that DIDN'T WORK for me (I've tried). So the only solution I know now is -no-xft.