Here you can find some hints and tricks - most of them
have been discussed on the KDE user forum...
First check if Your current qt installation is compatible with the
planned KDE (i.e. KDE2.1beta needs qt 2.2.1 or higher) - if not,
first uninstall old qt and install the proper version (to get info about installed qt components,
type 'rpm -qa | grep qt' at the commandline).
Although it is possible to have both KDE1.x and KDE2.x on the same machine
(SuSe has this as default), I (and not only me) recommend strongly
to NOT keep an old 1.x version when going to 2.x. - many
problems with messed up/double desktop icons etc. have been reported
to be related to this.
removing and old kde installation is easy - you can use this script.
The new KDE rpm's have to be installed in the correct order, using
'rpm -ivh name.rpm' :
- libmng*.rpm
- kdesupport
- kdelibs
- kdebase
- all the rest in any order
if you run into problems, namely dependency conflicts, try to find out what the
exact reason is (these this are often the result of not correctly uninstalled
versions of qt and kde libs) - when you are sure not to mess up things,
you can use 'rpm -ivh --nodeps' - this will ignore the mentioned conflicts,
but you may run into problems afterwards.
First step, as above, check/upgrade qt installation (if qt is installed via rpm,
don't forget qt-devel package ! (otherwise you will not be able to compile kde)
adjust env variable QTDIR correctly, or better, create a link to the directory where qt resides
(QTDIR=/usr/lib/qt, ln -s /usr/lib/qt-2.2.3 /usr/lib/qt).
For the rest, the installation procedure is well documented on
www.kde.org - here are my experiences with anoncvs/cvsup:
- anoncvs was not very reliable for me, I often ended up in broken
installations/missing files
- cvsup worked great for me so far, I recommend it! (see instructions
on www.kde.org how to get/install/use it)
always keep in mind that there is a chance to break your running kde by using this
method (the sources on cvs are not always in a state where everything matches
exactly) - so it is always a good idea to keep a set of proved-to-run
tarballs in a secure place!
This error has recurred several times after an installation of KDE via rpm.
It results in the effect, that the well known login screen from KDM
does not appear, instead an error message like 'respawn too fast...'
The problem lies in the packaging of the rpm's, sometimes the packagers assume
/usr/etc/X11 instead of /etc/X11 - KDM will not work.
This can be solved with a symlink:
- � su (or login als root)
- � ln -s /etc/X11 /usr/etc/X11
- � - thats it
A good starting point on this topic is www.konqueror.org/konqjava.html.
Anyway, it might not be so obvious what has to be done to get Konqueror
really work with java applets. The following steps are not necessary the only
possible procedure, but at least it is what I found out to work for me.
- get a Java runtime engine (Sun,IBM,Blackdown) -
I recommend the one from Blackdown -
www.blackdown.org
- go to jre bin directory (i.e. /usr/lib/j2re1.3/bin)
- start JavaPluginControlPanel an deactivate it
- configure konqueror to use the installed java (/usr/lib/j2re1.3/bin/java)
- deactivate 'use security manager'
At this point, it should be possible to run standard java applets
from konqi.
Another problem is to access applets using SSL encryption (widely
used by applets for internet banking) - these require in addition to
jre the installation/activation of jsse - jsse can be downloaded
for free (registration required) from www.sun.com.
RedHat: put 'KDE' in /etc/sysconfig/desktop
SuSe: in /etc/rc.conf DEFAULT_WM=kde, if GUI login via KDM desired,
DISPLAYMANAGER="kdm" and CHECK_INITTAB=yes
sometimes, kppp causes problems due to access restrictions/ppp options/routing etc. -
you may even come into a situation where you cannot use it at all,
e.g. your KDE installation is broken !
in these cases (and not only then), wvdial is an easy to use, reliable alternative.
There is even a good graphical frontend for KDE, qtwvdialer (found on apps.kde.com).
Here is a sample script to setup wvdial (SuSe provides sample
scripts for most providers in germany):
[Dialer Defaults]
Ask Password = 0
Baud = 57600
Dial Command = ATX3DT0W
ISDN = false
Idle Seconds = 180
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Modem = /dev/modem
[Dialer tonline]
Ask Password = 0
Compuserve = false
Country = Germany
Homepage = www.tonline.de
Password = XXXX
Phone = 0191011
Product = T-Online
Provider = Deutsche Telekom
Stupid Mode = true
Tonline = true
Username = xyz