> The X Window System is a network-based graphics subsystem.
Correct
> That is, unlike MS
> Windows, which is a standalone graphics subsystem, the X Windows System
> requires a network, even if it's only 127.0.0.1.
I don't think so, you can also use sockets, these are created in
/tmp/.X..... but sockets are also network ports.
> The X config files will have been corrupted, somehow. KDE has a magic cookie
> in /home/{user}.
It's difficult to see how the X config file (in /etc/X11/) can be
corrupted, other than by running sax2. Assuming ok hardware of course.
Forget the cookie - that gets created each time you log in for the first
time.
> > Could not read network connection list //.DCOPserver_ralph_0
> >
> > //.kde/share/config/krootimagerc
Those // are missing the /home/$USER/ bit in between.
> > No write access to $Home directory
Ouch, this will be causing the DCOP failure and dead KDE.
Is /home on a separate partition which isn't mounted? Why not mounted?
Do filesystem checks run at boot? What result?
Why does your hardware keep on freezing?
Volker
--
Volker Kuhlmann is possibly list0570 with the domain in header
http://volker.dnsalias.net/ Please do not CC list postings to me.
