nedvis: thanks for your comment, it helps a lot. But I'm not there yet.
I created a new user, martin2 (actually, copied an existing working user and tweaked it a bit). This works OK.
I replaced martin2's .kde and Desktop directories with martin's, and it still worked (except that it wanted to run the startup programs as martin instead of martin2).
I copied some files/directories from martin2 to replace the ones in my directory (which were moved elsewhere). These were:
.gconf .gconfd .gnome2 .gnome2_private .gnupg .gtk-bookmarks .mcop .mdk-folders .qt
martin2 still works and martin still doesn't!
I assume that there must be some other config files that KDE is reading which are in the martin home directory, but not in martin2. But what are they? I have about 450 dotfiles and directories in my home directory!
Which of these are personal files and which are system files???
I tried copying all the dotfile/directories from martin to martin2, but then I couldn't login to martin2: it hung on setting up process communications.
On martin, "kcmshell --list" produces this output:
The following modules are available:
kcmdf - Shows the disk usage of the mounted devices
kamera - Configure Kamera
kcmlirc - Configure your remote controls for use with applications
kwalletconfig - KDE Wallet Configuration
audiocd - Audiocd IO Slave Configuration
If I su to martin2 in a terminal window and run "kcmshell --list" I get:
Session management error: Could not open network socket
Session management error: Could not open network socket
kbuildsycoca running...
The following modules are available:
kcmaccess - Improve accessibility for disabled persons
language - Language, numeric, and time settings for your particular region
keyboard_layout - Keyboard Layout
keys - Configuration of keybindings
componentchooser - Choose the default components for various services
... plus dozens more!
Do you know what other config files KDE reads from?
Main Topics
Browse All Topics
by: nedvisPosted on 2009-01-31 at 09:24:45ID: 23517620
This workaround may help you diagnose whethet your KDE is broken or not .
While loged as a standard user in KDE session , try to open Run command
( or if you can open Kterminal or any terminal for that reason) and then type
-one command at time- this sequence of commands:
kcmshell desktop
kcmshell background
kcmeshell desktopbehavior
kcmshell screensaver
and so on, following the list of KDE modules errors you are getting in .xsession_erors file.
If you cannot get KDE modules running from command prompt go to next step.
Login as root to check whether you can get fully functional KDE desktop and X-session.
In case you can, it may be the sign that KDE configuraton for the standard user is currupt,
so you better carefully pick up all personal files from Home directory for user
account whith which you are having difficulties and then remove that user account.
Create new user account and login with newly creted user credentials.
If you can get fully functional KDE environment , as root copy all files you moved from
deleted user account elsewhere to new user home directory and - enjoy your oldie KDE 3.4.
If that does not help you may want to launch other desktop ( blackbox, ICE , TVWM ) and use Mandrake's software manager to remove and reinstall KDE.