GNOME Bugzilla – Bug 402360
gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Last modified: 2007-04-10 06:01:09 UTC
Steps to reproduce: 1. 2. 3. Stack trace: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 the computer crashes twice a day I have Fedora FC3 kernel 2.6.12-1.1381_FC3smp Other information:
This is not enough information to help diagnose the problem. Can you please describe what you were doing when the crash happened? Does it happen every time you try to login or only in some situations? It would help if you turn on enable=true in the [debug] section of your GDJ configuration. This will echo GDM debug messages to your system log (either /var/adm/messages or /var/log/messages depending on your OS). If you could attach GDM related debug messages to this bug report, then this would likely help. Also, Fatal X errors can be problems with your Xserver crashing. Can you also attach your /var/log/xorg.log and $HOME/.xsession-errors files, especially if they have any error messages in them when the crash happens?
Created attachment 81505 [details] messages file
Created attachment 81506 [details] Xorg file
It happens at diffrent times: once while clicking on back space once while reading mail
Note, if you press ctrl-alt-backspace your X session will be terminated, and you'll see that messages. That's by design. Is that's what's happening here?
no it happens randomly I just gave diffrent examples .like opening mail or pressing backspcae on an terminal
It sounds like your Xserver may be crashing, though I don't see any error messages in your Xorg.log. How about your $HOME/.xsession-errors file? Note that the xioerror_handler normally gets called when GDM gets a SIGTERM or a SIGINT from the Xserver. Normally if X crashes while your session is running, then the problem is not likely with GDM. The GDM daemon is just noticing that your Xserver has crashed and is restarting.
I don't think this is a GDM issue if the user is experiencing crashing during their running session. I'm closing this bug. If someone has information that this is, in fact, a GDM bug, please reopen.