Re: Gnome and X Failure -- HELP

["Tom Browder" <tom2 fwb asi srs com>]

Himanshu:  Thanks for the response, but I respectfully disagree.  The login process for gnome as it is interfaced with X is not very
well documnented for casual users, and I see little help for when things go awry.  There is a small  mention of corrective action in
the FAQ, but it doesn't point to where further to look if startx doesn't work.

I have seen the RH GUI problem several times during the last couple of distribution updates and the corrective action taken in the
past doesn't work.  All problems have been with the gnome desktop--not KDE.

Tom Browder

-----Original Message-----
From: Himanshu Gohel <gohel csee usf edu>
To: Tom Browder <tom2 fwb asi srs com>
Date: Thursday, December 28, 2000 12:42 PM
Subject: Re: Gnome and X Failure -- HELP


>Tom, please use appropriate Linux newsgroups/mailing lists for these
>topics...they have little to do with GNOME.
>
>Tom Browder wrote:
>>
>> I have an RH 7.0 setup which was working fine until yesterday.  Then I started a process that filled up my root partition.  I was
>> able to remove the rogue file and worked along OK until logout a the end of
>
>Perhaps the file wasn't really deleted.  Consider that some processes
>don't let go of the file.  You may think you've deleted it, but that
>process will happily keep writing to the file/inode/whatever internal
>structure it has available for that file on the disk.  You kill the
>process that created the file, then delete the file, and monitor it
>to make sure that the process is not re-spawned automatically.
>
>> I started up in single-user mode and cleaned out my .gnome* directories and tried again--same thing.
>
>It would seem that filling up the root partition should not affect
>a user's GNOME or any other directory.
>
>> Apparently something in /tmp got trashed at disk-full time and now my configuration is hosed.
>
>Anything in /tmp can and will get trashed on reboot (on many UNIX
>systems)
>It should not matter.  That really is a TeMPorary directory.
>
>My guess is your problem is elsewhere.  Start looking at system logs.
>
>Good luck,
>
>Himanshu
>
>