Quick Start Guide

6 Recover your individual application conguration data (including the Evolution
e-mail client data) by copying the ~/.gconf-ORIG-RECOVER/apps/ directory
back into the new ~/.gconf directory as follows:
cp -a .gconf-ORIG-RECOVER/apps .gconf/
If this causes the login problems, attempt to recover only the critical application
data and recongure the remainder of the applications.
A.2.4.5 Login Successful but KDE Desktop Fails
There are several reasons why a KDE desktop would not allow users to login. Corrupt-
ed cache data can cause login problems as well as corrupt KDE desktop conguration
les.
Cache data is used at desktop start-up to increase performance. If this data is cor-
rupted, start-up is slowed down or fails entirely. Removing them forces the desktop
start-up routines to start from scratch. This takes more time than a normal start-up,
but data is intact after this and the user can login.
To remove the cache les of the KDE desktop, issue the following command as root:
rm -rf /tmp/kde- user /tmp/ksocket- user
Replace user with your username. Removing these two directories just removes the
corrupted cache les. No real data is harmed using this procedure.
Corrupted desktop conguration les can always be replaced with the initial congu-
ration les. If you want to recover the user's adjustments, carefully copy them back
from their temporary location after the conguration has been restored, using the
default conguration values.
To replace a corrupted desktop conguration with the initial conguration values,
proceed as follows:
1 Switch to a text console by pressing [Ctrl] + [Alt] + [F1].
2 Log in with your username.
3
Move the KDE conguration directory and the .skel les to a temporary loca-
tion:
• For KDE3 use these commands:
mv .kde .kde-ORIG-RECOVER
mv .skel .skel-ORIG-RECOVER
• For KDE4 use these commands:
mv .kde4 .kde4-ORIG-RECOVER
mv .skel .skel-ORIG-RECOVER
256 Start-Up