abrt 1.0.7 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/seamonkey-2.0.3/seamonkey-bin component: seamonkey executable: /usr/lib/seamonkey-2.0.3/seamonkey-bin kernel: 2.6.31.12-174.2.22.fc12.i686.PAE package: seamonkey-2.0.3-1.fc12 rating: 3 reason: Process /usr/lib/seamonkey-2.0.3/seamonkey-bin was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine)
Created attachment 398181 [details] File: backtrace
#7 0x00e20be8 in __assert_fail (assertion=<value optimized out>, file=<value optimized out>, line=<value optimized out>, function=<value optimized out>) at assert.c:81 buf = 0xa0f49790 "seamonkey-bin: xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed.\n" #8 0x00888c0a in _XAllocID (dpy=0xb7546000) at xcb_io.c:378 ret = 4294967295 __PRETTY_FUNCTION__ = "_XAllocID" #9 0x00d2cc48 in XRenderCreatePicture (dpy=<value optimized out>, drawable=<value optimized out>, format=<value optimized out>, valuemask=<value optimized out>, attributes=<value optimized out>) at Picture.c:90 info = 0xb7551f20 pid = <value optimized out> #10 0x004e4f7a in _cairo_xlib_surface_ensure_dst_picture (surface=0xa0d2c760) at cairo-xlib-surface.c:887 No locals. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Reporter, can you please list steps we could use to reproduce this crash? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Sorry I can't be of much help. Seamonkey was running overnight and died while unattended.
Bug appears to have happened while painting. You could search upstream bugzilla for bugs with a similar crash signature, and point to this stack. If this was a one-time failure and there is no similar report upstream, this might not help much. I wish our builds would report crashes automatically to the upstream mozilla infrastructure, as the upstream mozilla builds do.
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.