Bug 56931 - Font display is corrupted, misspaced, or garbage appears in whitespace after install of X4.3.0
Summary: Font display is corrupted, misspaced, or garbage appears in whitespace after ...
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-07 02:19 UTC by Alistair Tonner
Modified: 2003-04-07 02:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alistair Tonner 2003-04-07 02:19:27 UTC
Version:            (using KDE KDE 3.1.1)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2 
OS:          Linux

************* NOT a KDE problem -- Filing for user reference *****************

   Process:
   Take working system with a base X 4.2.x working install
   Install and build either QT 3.1.1 or QT-copy from KDE
   (Note this is especially noticed if the original install of QT includes
	-xft on the configure line)
    Install and build KDE 3.1.1

    Later install/build X 4.3.0  
    ----> many many font display problems arise 
     You can overcome them by using the QT_XFT=0 env variable, but this 
      results in ragged fonts in some cases.
 
    Problem cause:   X 4.3.0 uses new version of XFT -

     I first rebuilt KDE 3.1.1 after installing X 4.3.0, but this only cleared some of the     issues and required me to install all fonts directly to each user (using Control Panel,     System Tools Font installer)
    However the real fix is to rebuild BOTH QT (with -xft) as well as KDE after eliminating all old copies of XFT in the X11R6 dir tree.

   There is a patch that Keith Packard has put out for QT but I did NOT require it for my copy of QT 3.1.1

   This *bug* is being file SOLELY for the purpose of guiding other users to a quick and easy solution - -there is NO implication of a bug in KDE as a result of this process.
Comment 1 Alistair Tonner 2003-04-07 02:20:32 UTC
Closing bug as resolved as I am filing this SOLELY for informational purposes