Created attachment 405085 [details] xorg log old Description of problem: If I remember correctly then before crash and X restart I closed Firefox, gedit and re-opened Firefox shortly thereafter. Typed something in search? And moved cursor a little bit to the upper right part of the screen. Version-Release number of selected component (if applicable): 2.6.33.1-19.fc13.i686 How reproducible: ? no idea Steps to Reproduce: 1. absolutely no idea. have system running for some time? 2. 3. Actual results: unexpected X server crash and restart Expected results: be stable, don't crash ;-) Additional info:
Created attachment 405086 [details] dmesg
Created attachment 406099 [details] xorg log old Another crash, just booted into Fedora. It happened while I tried to use Backspace to retype something into Firefox's search box.
Created attachment 406100 [details] xorg log old 2
Created attachment 406101 [details] dmesg 2
Created attachment 415902 [details] Xorg log I can't get anything more than the seg fault. I have all the debug pkgs installed. Direction to get more info would help me out, though I'll try it wired when I get a chance. (the crash disconnects the desktop-started wireless... duh ;-)
Backtrace: [ 19007.922] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e515c] [ 19007.922] 1: /usr/bin/Xorg (0x8047000+0x5e056) [0x80a5056] [ 19007.922] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xc4440c] [ 19007.922] 3: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x180000+0xd2e8) [0x18d2e8] [ 19007.922] 4: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x180000+0x4263) [0x184263] [ 19007.922] 5: /usr/lib/xorg/modules/libexa.so (0x1cb000+0x8748) [0x1d3748] [ 19007.925] 6: /usr/lib/xorg/modules/libexa.so (0x1cb000+0xe102) [0x1d9102] [ 19007.925] 7: /usr/bin/Xorg (0x8047000+0xd4957) [0x811b957] [ 19007.925] 8: /usr/bin/Xorg (CompositePicture+0x290) [0x810e980] [ 19007.925] 9: /usr/bin/Xorg (0x8047000+0xcdba5) [0x8114ba5] [ 19007.925] 10: /usr/bin/Xorg (0x8047000+0xca734) [0x8111734] [ 19007.926] 11: /usr/bin/Xorg (0x8047000+0x26e27) [0x806de27] [ 19007.926] 12: /usr/bin/Xorg (0x8047000+0x1b565) [0x8062565] [ 19007.926] 13: /lib/libc.so.6 (__libc_start_main+0xe6) [0x55dc96] [ 19007.926] 14: /usr/bin/Xorg (0x8047000+0x1b151) [0x8062151] [ 19007.926] Segmentation fault at address (nil) [ 19007.926] Fatal server error: [ 19007.926] Caught signal 11 (Segmentation fault). Server aborting
mcepl 2010-05-24 11:36:15 EDT xorg-x11-drv-nouveau Why? In my case, nouveau is not involved.
(In reply to comment #7) > mcepl 2010-05-24 11:36:15 EDT xorg-x11-drv-nouveau > > Why? > In my case, nouveau is not involved. Yes, because your backtrace is completely different: Backtrace: [ 2216.783] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80e51dc] [ 2216.783] 1: /usr/bin/X (0x8047000+0x5e176) [0x80a5176] [ 2216.784] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xc4640c] [ 2216.784] 3: /lib/libc.so.6 (0x282000+0x792c6) [0x2fb2c6] [ 2216.784] Segmentation fault at address (nil) [ 2216.784] Fatal server error: [ 2216.784] Caught signal 11 (Segmentation fault). Server aborting Please file a separate bug with attachments * your X server config file (/etc/X11/xorg.conf, if available), * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
(In reply to comment #8) > (In reply to comment #7) > > mcepl 2010-05-24 11:36:15 EDT xorg-x11-drv-nouveau > > > > Why? > > In my case, nouveau is not involved. > > Yes, because your backtrace is completely different: > > Backtrace: > [ 2216.783] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80e51dc] > [ 2216.783] 1: /usr/bin/X (0x8047000+0x5e176) [0x80a5176] > [ 2216.784] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xc4640c] > [ 2216.784] 3: /lib/libc.so.6 (0x282000+0x792c6) [0x2fb2c6] > [ 2216.784] Segmentation fault at address (nil) > [ 2216.784] > Fatal server error: > [ 2216.784] Caught signal 11 (Segmentation fault). Server aborting > > Please file a separate bug with attachments > > * your X server config file (/etc/X11/xorg.conf, if available), > * output of the dmesg command, and > * system log (/var/log/messages) > > to the bug report as individual uncompressed file attachments using the > bugzilla file attachment link above. > > We will review this issue again once you've had a chance to attach this > information. > > Thanks in advance. https://bugzilla.redhat.com/show_bug.cgi?id=598761
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.