Fedora 4 no logon screen - blank screen with X
 

I was trying to install gnome-system-tools and the many dependancies it has. the last one I tried to install was pango apparently it installed, and then I rebooted becouse the rpm install windows would all of a sudden dissappear without saying weather or not anything was installed.
I havent been able to start my computer since. I only get to the blank screen with an x. Once and a while a text dialogue appears and says "The display server has been shut down about 6 times in the last 90 seconds, it is likely that something bad is going on. I will try again to restart the display server in 2 minutes.0"

What the hell happend???!!! nobody else seems to have this problem!!

PLEASE HELP!!!

Check /var/log/Xorg.0.log for errors.

I did, and there was nothing that said error.

Post the file (in a quote block), and we'll take a look.

Too late I could not wait for an answer anymore, I've re-installed. But Just in case this happens again what would cause this?

The nature of the error will be in /var/log/Xorg.0.log. An error doesn't always have the word 'error' in it.

Thanks for your help I'll remember that the next time.

i also have almost the same problem.but my problem appear after i run fsck when os running.now when i boot its shows thats some files missing.

when boot:

/etc/rc3.d/s54hproj
/usr/sbin/ptal_init
/etc/rc3.d/s56xinetd
/etc/rc3.d/s56xinetd
krb5.sh file missing

/etc/rc5.d/s01sysstat
/usr/lib/sa/sadc

for your info,my linux is a file server with samba setting. now samba is available, only that i just cant get in the Xwindow...i use kde last time. i press Ctl+alt+f7 blank screen come out....

Help me, very urgent now

This should really be in a separate thread, since its a completely different problem.

You can identify the packages that you need to reload, by querying the rpm database for the missing files. For example,

rpm -qf /usr/lib/sa/sadc

This will tell you the package that contains the deleted file. You can download it, then force a reinstall:

rpm -Uvh --force xxx-y.x.rpm

i have follow your instruction and get some of this package

if i reinstall...would it effect to my comp samba server setting?

this what i get thats

krb5-devel-1.3.4-7
sysstat-5.0.5-1
chkconfig-1.3.11.1-1
initscripts-7.93.2-1
file system-2.3.0-1

if i reinstall above package any effect?for your info i use fedora core 3

/dev/VolGroup00/LogVol00 as root

The effect is that your system will have integrity, it does not now.

Existing configuration files that have been customized should not be replaced. Rpms are configured to create an "xxx.conf.rpmnew" or "xxx.conf.rpmsave" file, if an existing configuration file is found.

ok...i have try the method..but stil can't success...i press alt+f7 the mouse not spinning,but can see the movement but stil appear in blank screen.

You will need to log off and restart X (ctl-alt-backspace), then check /var/log/Xorg.0.log for errors. Repeat the process if additional missing files are reported. If it continues on more than you are willing to put up with, then a re-install may be easier.

I have the same problem as yorgmeister. I am running Ubuntu 6.06, and i got it when i last update. When the login window is supposed to pop up my GDM crashes few times and the linux switches between terminal and GUI.
I dont know what couses this, but i believe that it starts to happen when i configure the "login window" and reboot.
I am posting you my Xorg.0.log file and i hope you will be able to help me without reinstalling my Ubuntu.

ht tp://0mg.91neg.com/Xorg.0.log

My graphic device is Ati Radeon 9550, CPU: AMD Semprom 2800+.

I hope this is enough.

10x for the help :)

Omg: the errors I see in your log are:

(EE) xf86OpenSerial: Cannot open device /dev/wacom

If that's your only mouse device, then X will not start until you get it working again (or configure a different mouse).

I have encountered that error on Fedora 8. It turned out that I ran out of disk space. I ran the Fedora 8 cd in rescue mode. Mounted / and deleted a large file. That solved my problem. It could have just said you don't have enough disk space to start the display. I think the error was also saying that the greeter application appears to be crashing trying a different one.