[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-linux-e
Subject:    [SLE] startkde / xft2 / antialiasing
From:       "Paul C. Leopardi" <leopardi () bigpond ! net ! au>
Date:       2003-04-10 21:54:58
[Download RAW message or body]

Hi all,
Ever since updating my SuSE Linux 8.1 to XFree86 4.3.0, KDE 3.1.1 and QT 
3.1.2, I have had problems with antialiasing and with fonts. I've been trying 
to fix these, but have come to the realization that I don't understand how 
xft2, fontconfig, fonts-config, KDE font configuration, QT anti-aliasing 
settings and KDE anti-aliasing settings interact.

I finally got anti-aliasing to work after I commented out some of the fonts in 
my XF86Config file, corresponding to empty font directories. This eliminated 
the following messages:
Could not init font path element /usr/X11R6/lib/X11/fonts/local, 
removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/kwintv, 
removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID, 
removing from list!
Since I don't understand the interaction of all the different font 
configurations, I am not sure I did the right thing.

My most recent problem began because, after I had antialiasing working again, 
I ran YoU to install a security fix. YoU runs SuSEconfig, which configures 
fonts and runs fonts-config. After having done this, once I logged out and 
logged back in, I lost anti-aliasing.

In an effort to try to figure out what is going on, I looked at 
/opt/kde3/bin/startkde
I did notice the following in startkde:
# [...]
# The user's personal KDE directory is usually $HOME/.kde3, but this setting
# may be overridden by setting KDEHOME.
# [...]
# Activate the kde font directories.
# [...]
usr_odir=$kdehome/share/fonts/override
usr_fdir=$kdehome/share/fonts
# [...]

This looks like a bug, since $kdehome is not set anywhere.

Versions:
XFree86-4.3.0-17
freetype2-2.1.3-36
qt3-3.1.2-6
kdelibs3-3.1.1-28


OK. Question time
1. Is anyone else having problems with anti-aliasing after updating SuSE 8.1 
to Xfree86 4.3.0, QT 3.1.2 and KDE 3.1.1? What is the fix for this?

2. Is there a FAQ or howto which documents installation and configuration of 
fonts, which is valid and up to date with respect to these versions of 
software? Does it document the interaction between xft2, SuSE fonts-config, 
the KDE Font Installer, xfs and anti-aliasing settings in QT and KDE?

3. Why is $kdehome used in startkde rather than $KDEHOME ? Is this a bug?

4. I noticed that in KDE Font Installer, in Settings, there is a selection in 
"Refresh font list with:" that says "/etc/rc.d/init.d/xfs restart", but the 
xfs script is actually /etc/init.d/xfs. Is this a bug in KDE Font Installer?

Best regards

-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com


[prev in list] [next in list] [prev in thread] [next in thread]