Whole distro breaks down over 30 minute span.

[Smart Guy]

I agree with Darek's observation. From non-root user, applications 
either dont start or start very slowly. Shutdown has not worked properly 
for me, unless i push power button of computer.

draek at shaw.ca wrote:

>Installation of Fedora Core 2 completed without problems or error
>messages. Login works fine at the start, GNOME 2.5.91 starts. Not all
>RedHat configuration tools work, like network panels, or most of the
>"System Settings" and "System Tools" when running these from a console
>window using my non-root user, i do not get a prompt for root password,
>but a text error message saying:
>
>Could not set exec context to user_u:sysadm_r:sysadm_t.
>
>sometimes its not sysadm_r but rpmn_t or something. Looks like non-root
>user is not allowed to run anything. If i run these tools after using
>"su" then I can run them.
>
>Eventually, no GNOME apps will start, including Ximian Evolution, giving
>a large error message about not being able to communicate with the
>network. Eventhough it works at first.
>
>And in the end, I cannot even log in to a session in GNOME or log out
>for that matter. The shutdown sequence shows tons of errors about
>partitions not being found, and large error outputs that I cannot
>copy/paste. I can however log in/out in the beginning after a clean
>reboot. If I reboot my machine after all these errors, everything works
>fine for a while, until i start not being able to run programs etc, like
>described above.
>
>This is a clean FC2T2 install, no additional programs have been
>installed into the system as of yet.
>
>>From what I understand so far in Linux, there seems to be a problem with
>permissions in FC2T2, the non-root users cannot run everything, lots of
>programs don't start without errors, and eventually the distro cannot be
>used any longer.
>
>The reason why I post this message is to see if anyone knows of an
>already known issue that is causing my problem. I'm not sure if I
>provided enough information, if there is something you need in order to
>help me diagnose the problem, please email me at draek at shaw.ca and I
>will do my best to acquire the info needed.
>
>I'm in the process of attempting to do a full "yum -y update" to see if
>that will fix anything.
>
>
>  
>