Ronald Wiplinger
Hi,
my server stopped and I had to use the reset button ;-( After rebooting I get the message "Could not start kdeinit - Check your installation.
What should I do to fix that?
bye
Ronald
Hi Ronald,
Sounds like your are running KDE ? Right ???
Assuming your are, it appears that after the crash,
KDE is viewing it as a new install but the "old" stuff
is giving problems...
Curtis Rey last July wrote up a receipe for how to clean out
your temp files and mcop after a new install.
It can be found at:
http://lists.suse.com/archive/suse-linux-e/2003-Jul/2981.html
I am assuning SuSE starts up for you and you can get into
a virtual terminal such as: "ctrl+alt+F1"
*** Method for cleaning out /tmp files after KDE upgrade ***
If you still have trouble, then hit ctrl+alt+F1
type "root"
then enter the psswd,
then init 3 (or telinit 3)
(you may have to reenter root's password)
then rm -rf /tmp/*
and then the same with rm -rf /tmp/.*
What this does is remove the tmp files and other config files
that may have permission sets and pointers to old configs
and the cookie for X.
Don't worry they will be recreated when you log back in via kdm
Then go into the /home/<user name>
and type rm -fr .mcop and
rm .mcoprc,
then go into /home/<user name>/.kde and
rm *-<host name>
then rm -rf /tmp/*
in my case it rm *-Crusher-1
which removes the symlink to /tmp/socket-Crusher-1
and /tmp/tmp-Crusher-1.
Now, if you remove/clean out the /tmp (don't rm the /tmp dir itself)
and removed the .mcop and mcoprc
as well as the .kde/sockets-<host name>
and .kde/tmp-<host name> files
type from tty1 (crtl+alt+F1) do "init 5 or telinit 5
and you'll see the xserver restart.
then ctrl+alt+F1 from the kdm screen and type exit or logout.
then crtl+alt+F7 back into kdm login,
login to users account.
Then do as above in the konsole with "sux -".
Forgive me if this is redundant, I don't know you experience level.
Like I said, sometimes, after updates, host name changes, etc
you have to clean out these files. It used to be a must with kde upgrades,
and I still do it from time to time when kde get cranky.
HTH Curtis.
*****************************************************
From: Anders Johansson
and the cookie for X.
No, the X cookie is stored in $HOME/.Xauthority If "sux -" doesn't work, su, rm /root/.Xauthority , exit , sux. Then it should work. Getting to be a FAQ. ===== [gar@gboxen1 gar]$ locate .Xauthority /home/carolene/.Xauthority /home/gar/.Xauthority [gar@gboxen1 gar]$ Also: /root/.Xauthority is there, just not found from gar@boxen1 ************************************************************* (Curtis back in reply to Anders):
If sux doesn't work, su, rm /root/.Xauthority , exit , sux. Then it should work.
Getting to be a FAQ.
I got it backwards, or sideways, or.....All right already :P Cheers, Curtis. :) I did a little editing on the above, so reading the original would be good. YMMV. Friendly greetings, Gar -- In the Beginning was the Command Line ---Neal Stephenson -- __________________________________________________________________ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need.