Rock wrote:
> On Tue, 16 Apr 2013 00:21:33 +0000, Rock wrote:
>
>
>> Is there a Desktop crash log somewhere?
>
>
> Given that the advice was that X was crashing due to Nvidia
> driver mismatch problems after my "yum update", I took a look
> at the ~/.xsession-errors log file before and after the crash.
>
> And, you seem to be correct: The xsession is crashing when
> using Firefox (but not Chrome):
>
> Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0'.
> nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
> polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
> nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
> rhythmbox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
> gpk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
> pan: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
> gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
> gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
> gnome-terminal: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
> [14555:14555:0415/175602:ERROR:chrome_browser_main_x11.cc(62)] X IO error received (X server probably went away)
Those messages are a result of Xorg crashing - i.e. various X11 apps
complaining that Xorg has gone away ...
Any Xorg crash details will be in /var/log/Xorg.?.log - however, if Xorg
has restarted since the crash, then the error should be in
/var/log/Xorg.?.log.old
The error may also be in one of the log files in /var/log/gdm/
James Pearson
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
