KDE 3.1->3.2 upgrade woes

[Chad Kittel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 26 April 2004 15:54, Erik Søe Sørensen <eriksoe at daimi.au.dk> wrote:

I didn't have any of the troubles you mentioned or any other troubles 
personally during my upgrade on 24Apr04. I am still using xfree86-beta though 
which might make a difference.  It would be interesting to learn why it 
worked on some and not others... 
See notes below

> I had two kinds of QT3 building problems:
>    First(?) I had to remove '--xft' from the configure args; this may be
> because I have misconfigured XOrg when I installed that? (Still, if that
> was so easy for me, then using XFT should be optional for QT.)
Not using XOrg, but had no compile/build/install errors or any kind along the 
way.

> KDE forgot my shortcut key settings
I don't have any of these, so I cannot attest to this.

> KDM lost its background.
I did not experience this.

> Then there's anti-aliased fonts.  It took me some time to figure out
> that I had to lin font-config.
I had fontconfig installed prior, so maybe that is why I didn't experience any 
anti-aliasing issues?

- -v3rt1g0

- -- 
Chad R. Kittel
 E-Mail: vertigo at wi.rr.com
 Running: Lunar-Linux (kernel: 2.6.6-rc1-mm1)

- ------------------------------------------------------
sushi, n.:
	When that-which-may-still-be-alive is put on top of rice and
	strapped on with electrical tape.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAjZaM+j8p7lVzKmsRAlbkAJ9mG1GrTU5M4KmDCrKMmiTU3ib9yACgvmtf
eN7Ua/vs/3bzZKABryXpfCk=
=Gaea
-----END PGP SIGNATURE-----