On Thu, 16 Dec 1999, [EMAIL PROTECTED] wrote:
> Check if there is a file /etc/nologin
>
> If there is, remove that puppy.
>
> rm -f /etc/nologin
>
Alas, that's not it.
Here are some further developments. kde only runs for a short while (A few
minutes) then exits. As it's comming up, it returns:
kpanel: waiting for windowmanager
stretchPixmap 30x3 to 120x3
stretchPixmap 30x3 to 120x3
stretchPixmap 30x3 to 3x120
stretchPixmap 30x3 to 3x120
kCharset: Wrong charset!
kvt:invalid foreground color
kvt:will use black-on-white instead
I can open the built in browser to the home directory (/root) and
explore the subdirectories, but when I try to move up in the directory
structure, I get.
xauth: (argv):1: bad display name "schlenoff4:0" in "add" command
Xlib: Connection to "0:0" refused by server
Xlib: Invalid MIT_MAGIC_COOKIE-1 key
(I can keep hitting the up button and keep getting this message. Then
it all comes down with:)
kioslave: cannot connect to X server:0
If this server is no longer running remove /tmp/.X0-lock and start again.
And I'm back at the console, looking for consolation.
Could this be related to having changed my hostname several times
before stuck? When I found the "right" way to do it, I was warned that
changing you host name on the fly could cause som serious problems. I noticed
that there are several files in the /tmp directory that reference my old host
name, and several that have the new host name in the title. They all have the
format:
kfm_X_Y_hostname_0
and
kio_X_Y_hostname_0
Where X and Y are numbers. X is either 0 or 500, so I assume it's a
userid. "hostname" is split about evenly between my new and old hostnames. I'm
tempted to delete them all, but I'll wait until I hear from the gurus before I
do anything rash.
I dutifully went in and removed the lock file. I then logged out and tried to
log back in via the normal route into kde. I hung again, and I walked away in
deffeat, but when I came back, I was in! I don't think the problem is fully
fixed, but at least I can get into system. There still is something that is
hanging when I log in, but it must be timing out.
Man this learning curve is getting steep!
Thanks again for all the help and info.
