Novell LINUX ENTERPRISE SERVER 10 - INSTALLATION AND ADMINISTRATION 11-05-2007 Installation Manual page 943

causes GNOME to initialize a new one. Although the user is forced to reconfigure
GNOME, no data is lost.
1 Switch to a text console by pressing Ctrl + Alt + F1 .
2 Log in with your username.
3 Move the user's GNOME configuration directories to a temporary location:
mv .gconf .gconf-ORIG-RECOVER
mv .gnome2 .gnome2-ORIG-RECOVER
4 Log out.
5 Log in again, but do not run any applications.
6 Recover your individual application configuration data (including the Evolution
e-mail client data) by copying the ~/.gconf-ORIG-RECOVER/apps/ direc-
tory 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 reconfigure the remainder of the applications.
51.4.4 Login Successful but KDE Desktop
Fails
There are several reasons why a KDE desktop would not allow users to login. Corrupted
cache data can cause login problems as well as corrupt KDE desktop configuration
files.
Cache data is used at desktop start-up to increase performance. If this data is corrupted,
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 files of the KDE desktop, issue the following command as root:
rm -rf /tmp/kde-user /tmp/socket-user
Common Problems and Their Solutions 925