Problem fixed:
I got some help from the Gnome list and was told to delete "~/ICEauthority" and
that did it apparently it is a but in my version of Gnome.
Thanks to all who responded
Michael
Michael McLeod wrote:
> I tried your solution, I did find some old files and deleted as you said, but
> darn it that didn't fix the problem. This problem is unique to root and no
> other user (I only have 1) KDE as root works fine. So I assume it is
> something with gnome root. Any other ideas? This has happened before and I
> reloaded RH 6 completely, this is not disaster, just inconvenient as I am new
> to Linux and still very much in the learning stage. But for learning and
> practical reasons I would like to solve it.
> Michael
>
> "John P. Verel" wrote:
>
> > Two. First, to prevent core dumps, put ulimit -c 100000 in your
> > /etc/profile. This will limit the size of core dumps to whatever
> > number you specify, e.g. 100000
> >
> > Second, Gnome (on my machine) leaves old files (I think they are lock
> > files) laying around my ~/.gnome directory. They look like
> > ".gnome-smproxy-nLhsKF" I delete all but the one which obviously
> > corresponds to the current session. This seems to make a big
> > difference.
> >
> > John
> >
> > On 05/22/00, 10:23:45PM -0400, Michael McLeod wrote:
> > > I am using RH 6 and yesterday while trying to solve a printing problem I
> > > was browsing in linuxconfig, suddenly my computer rebooted and went to
> > > the login page as usual. I logged in as usual but then the problem
> > > began, it took a bit longer for enlightenment to finish loading, the
> > > Gnome splash screen stayed on for about 3 times longer than usual and it
> > > took Gnome what seemed an enormous amount of time to come up (maybe 4
> > > min). Now this always happens unless it do a control+alt+backspace and
> > > restart login, then it goes as fast as usual. Once up Gnome seems to
> > > work as fast as usual but tends to experience "Core dumps".
> > > Any suggestions?
> > > Michael
> > >
> > >
> > > --
> > > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > > as the Subject.
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.