Hello, probably since I did the last upgrade to kde3.4.2 on a suse9.3 system one particular user has a problem running KDE. Only this user has this problem other users can work without problems. The problem is that after the user has started up KDE (from kdm) he cannot *type* anything no matter if he tries a terminal window or tries to type in a URL in konqueror or anything else. The keyboard seems not to be there. Even numlock or CTR-ALT-F{x} or CTRL-ALT-BACLSPACE does not do anything. So the only way to leave this login is to terminate it via the KDE-Menue which works fine. In short words: You can do anything you want by *clicking* but you cannot do anything by *typing*. When I move the users .kde dir to .kde.old and start a new login so that a fresh .kde dir is created everything works again. The trouble is that going this ways the users looses quite everything, from konqueror bookmarks, severel mail accounts in kmail, passwords in kwallet and probably many things more I don't see now. So does anyone see a way to get kde working again without loosing the complete KDE setup of this user. Which of those hundreds of config files in .kde might be responsible for the keyboard lockup? Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke@uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------