Hi,
I looked in /var/log and also created
the X.out file, and I didn't notice
any outstanding errors that would
point me to the right direction. I also
deleted the .gnome directory and it still
comes up with the gray screen. Lastly,
I tried reinstalling gnome itself and
there is still a gray screen. Because
of the lack of errors listed, it almost
seems as if gnome isn't starting up at all.
The gray screen is normally the first thing
that you see, and after a second or two,
the panel and icons come up, and a
background replaces the gray.
Perhaps I could try starting everything step
by step and seeing the problem? Or, what else
should I do?
Thanks again.
Warren
> -----Original Message-----
> From: Benjamin Scott [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 05, 2000 11:24 AM
> To: Greater NH Linux Users' Group
> Subject: Re: X init problem
>
>
> On Wed, 5 Jul 2000, Mansur, Warren wrote:
> > Now, whenever I type 'startx', X starts to boot, but then
> hangs at the gray
> > screen. The panel or the desktop icons don't appear, and I
> am unable to do
> > anything. The mouse cursor moves around, but that's it.
>
> Sounds like the X display server itself is starting, but the desktop
> environment (window manager, etc.) is failing and/or hanging.
>
> > I ran XF86Setup and restored everything to defaults.
>
> ... more evidence that the X server is fine ...
>
> > I'm running RedHat 6.2.
>
> What desktop environment and/or window manager are you
> using? GNOME? KDE?
> Enlightenment? Sawmill? FVWM?
>
> > Does anyone have any clue what this could be and how to fix
> it? Any help
> > would be appreciated.
>
> First, if you don't know, the magic keystroke to shutdown
> the X server is
> [CTRL]+[ALT]+[BACKSPACE]. The X server itself does a clean
> shutdown, but any
> clients will most likely abort as their connections are
> broken. But it beats
> rebooting the machine any day.
>
> Check your system logs (usually in /var/log) for any
> messages emitted by
> failing programs.
>
> Look in your home directory. Some Xclients scripts
> redirect output to error
> files. Sometimes they are dot (hidden) files. File names
> vary but usually
> have "errors" in them somewhere. You may find clues there.
>
> Is your shell bash? If not, get into bash (run "bash").
> Once in bash, run
> the command "startx > X.out 2>&1". That will redirect all
> output of any
> X-related programs to the file "X.out". Once any activity
> has completed, use
> above magic keystroke to exit back out, then examine the file.
>
> If none of this leads you anywhere, give a yell, and we can
> try manually
> starting the clients step by step.
>
> --
> Ben Scott <[EMAIL PROTECTED]>
> Net Technologies, Inc. <http://www.ntisys.com>
> Voice: (800)905-3049 x18 Fax: (978)499-7839
>
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
