well the errors make complete sense, a file isn't writable if it doesn't exist and each file mentioned is relative to the /home/user1(2) directories that have been removed, kde needs files in the users home directory to start, it's interesting that you can start icewm without a home directory but obviously once you do you can't access kde files since there aren't any for that user, i'm assuming that when you say the new user3 can log in ok you mean into kde, since it has a home directory? since the home directories for users 1 and 2 have gone you don't lose anything by deleting the users and recreating them - since you've already lost it :( , assuming you can run mcc from the user3 login (with the root password root of course) then you can delete the problem users and recreate them, this doesn't explain why their directories were deleted in the first place, what mandrake ver. are you? and what was the program you were trying to install when it all went pear shaped?
bascule On Sunday 20 Feb 2005 11:31, john wrote: > Message 1: "Could not read network connection list. > //.DCOPServer_localhost_0." �Message 2: "Will not save configuration- > Configuration file //.kde/share/config/ksplashrc not writable. > Configuration file //.kde/share/config/kdeglobals not writable." Message > 3: "No write access to $HOME directory-Kde is unable to start." I can > log in to icewm but still have no access to any kde files. User 3 is the > new one and login is ok. The file /Home now only lists user 3. The files > /home/user1 or /home/user2 have been removed -- "Ah, " said Arthur, "this is obviously some strange usage of the word safe that I wasn't previously aware of. "
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
