abrt 1.0.2 detected a crash. Comment: Don't remember now. Attached file: backtrace cmdline: /usr/bin/python -E /usr/bin/sealert -s component: python executable: /usr/bin/python kernel: 2.6.31.9-174.fc12.i686 package: python-2.6.2-2.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted)
Created attachment 381812 [details] File: backtrace
Thank you for reporting this bug. How reproducible is this problem? What is the output of running the following command? rpm -q setroubleshoot-server gtk2 cairo Looking at the backtrace, it looks like this assertion failed inside frame 3 of the program's single thread inside _XAllocID: xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed. and this is happening deep inside cairo, whilst using the ClearLooks theme to draw a box ("clearlooks_draw_gummy_gradient" in frame #18) Reassigning component from "python" to "gtk2"; I hope the gtk2 maintainer can diagnose this further.
Ok, here is the output. Oddly, the print dialog box popped up when I ran the "rpm -q setroubleshoot-server gtk2 cairo" command. Is this supposed to happen? [don@bluefic ~]$ su Password: [root@bluefic don]# rpm -q setroubleshoot-server gtk2 cairo setroubleshoot-server-2.2.52-1.fc12.i686 gtk2-2.18.5-4.fc12.i686 cairo-1.8.8-3.fc12.i686 [root@bluefic don]# Don
XAllocId assertion -> libxcb
xcb_io.c is actually a libX11 file not a libxcb file. May well be the same as https://bugs.freedesktop.org/show_bug.cgi?id=27552 , though all sorts of different locking problems in libX11 or X extension libraries could trigger this assertion failure.
*** Bug 579643 has been marked as a duplicate of this bug. ***
Still occurring with F13 based the last duplicate I marked (which had several duplicates itself)
My assumption is that the Assigned To here is either, 1. Deceased, or 2. Not interested.
Or, 3. Assigned To is busy, and has other priorities! My apologies for the earlier remark - I have bugs with no activity for months and assumed otherwise. But I see updates by sandmann as recently as 2010-08-24 09:11:27 EDT. I'll try to help by marking duplicates. Sorry for the noise.
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.