[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: (no subject)
- From: Bret Hughes <bhughes elevating com>
- To: seawolf-list redhat com
- Subject: Re: (no subject)
- Date: Thu, 31 May 2001 23:22:44 -0500
Michael Schwendt wrote:
>
> On 2001-05-31, Ted Clark wrote:
>
> >> can someone point me in the right direction
> >
> >Sounds like you might be crapping out loading the X xerver. Try
> >pressing <ctrl><alt><backspace> on the gray screen, see what happens.
> >It should throw you back to a Linux console screen.
>
> Hmmm, if a display manager is running, this would just fire up
> that one again and again. Hence I suggest CTRL+ALT+F1 (or F2,F3
> any virtual console), then log in as root, and run
>
> rpm -qa | grep XFree | xargs -t -n 1 rpm --verify
>
> to see whether any binaries in the XFree86 packages turn up as
> damaged (notice the '5' then for MD5 checksum mismatch). Erasing
> faulty packages and re-installing them should fix any problems with
> XFree86.
>
> And if XFree86 is not the only damaged component, the same can be
> done with any other package.
>
Does this happen with all users?
I have seen similar doings with corrupted files in /tmp and some of the
files in hidden directories in the user's home dir. Seems like the
.gnome* ones were suspect at the time. If all progs verify ok go to the
VC using the ctrl-alt-F1 or what ever as suggested above and rename the
.gnome files and remove the files in /tmp owned by the user. then go
back to X (ctrl-alt-F7) and do the ctrl-alt-backspace deal.
Now that I think about it the home dirs are probably not the issue since
you are not getting a chance to login. I would clean up the tmp stuff
and see what happens. If you still ave problems it might be easier to go
to runlevel 3 (telinit 3 as root)and start X manually as a user
(startx). at least you might get a chance to see the error messages
easier.
HTH
Bret
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]