Created attachment 369157 [details] .xsession-errors file from first crash First of all, I set it to the gnome-session component but I'm not really sure. Anyway, my session crashes, so that should be a safe bet from which to move the actual component at fault. Description of problem: Session crashes unexpectedly. This already happened to me twice in two days, it seems random and I have no idea how to reproduce it. What I do know is that when it happens, running apps are: - Epiphany with a tab opened on GMail - Empathy, no conversations ongoing, only the tray icon showing - Rhythmbox, playing music - Aisle Riot Solitaire - Liferea Version-Release number of selected component (if applicable): gnome-session-2.28.0-2.fc12.x86_64 epiphany-2.28.1-1.fc12.x86_64 empathy-2.28.1.1-3.fc12.x86_64 rhythmbox-0.12.5-8.fc12.x86_64 gnome-games-2.28.1-1.fc12.x86_64 liferea-1.6.0-1.fc12.x86_64 I attached the two .xsession-errors files that I got, one for each crash.
Created attachment 369158 [details] .xsession-errors file from second crash
If your whole session suddenly disappears, it might well be that your X server crashed. If that is the case, there should be a stacktrace in the latest Xorg.log in /var/lib/messages
Right, X is dying: gnome-settings-daemon: Fatal IO error 104 (Connection reset by peer) on X server :0.0. gnome-session: Fatal IO error 104 (Connection reset by peer) on X server :0.0. Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'. nautilus: Fatal IO error 104 (Connection reset by peer) on X server :0.0. polkit-gnome-authentication-agent-1: 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.0. epiphany: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. sol: Fatal IO error 104 (Connection reset by peer) on X server :0.0. npviewer.bin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. No protocol specified Cannot open display: Would you mind attaching your /var/log/Xorg.0.log?
Unfortunately, I don't have the Xorg.0.log from the crash anymore. I'll attach it if it happens again.
Created attachment 369551 [details] Xorg log from the third crash Happened again, here is the Xorg log.
Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49e8d8] 1: /usr/bin/Xorg (0x400000+0x619c9) [0x4619c9] 2: /lib64/libpthread.so.0 (0x36b8600000+0xefa0) [0x36b860efa0] 3: /usr/lib64/xorg/modules/libfb.so (fbBlt+0xa54) [0x7fa5b08a3054] 4: /usr/lib64/xorg/modules/libfb.so (fbCopyNtoN+0x268) [0x7fa5b08a5c58] 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fa5b12de000+0x5ae5a) [0x7fa5b1338e5a] 6: /usr/bin/Xorg (miCopyRegion+0x28d) [0x54575d] 7: /usr/bin/Xorg (miDoCopy+0x44a) [0x545c6a] 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fa5b12de000+0x5a6f0) [0x7fa5b13386f0] 9: /usr/bin/Xorg (0x400000+0xd3f18) [0x4d3f18] 10: /usr/bin/Xorg (0x400000+0x2b1ec) [0x42b1ec] 11: /usr/bin/Xorg (0x400000+0x2c69c) [0x42c69c] 12: /usr/bin/Xorg (0x400000+0x21cfa) [0x421cfa] 13: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x36b821eb1d] 14: /usr/bin/Xorg (0x400000+0x218a9) [0x4218a9] Segmentation fault at address 0x1cff Fatal server error: Caught signal 11 (Segmentation fault). Server aborting
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.