abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/python /usr/bin/system-config-services component: system-config-services executable: /usr/bin/python kernel: 2.6.32.9-70.fc12.x86_64 package: system-config-services-0.99.42-1.fc12 rating: 4 reason: Process /usr/bin/python was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine)
Created attachment 399797 [details] File: backtrace
Not sure if this is related to bug #572999. Changing component to python for triaging of whether this is a problem in a native module (likely contenders are gtk, glib, gobject, dbus) or the interpreter.
Thank you for reporting this bug. How reproducible is this problem? If you run the program from a terminal, is an error message printed? What is the output of running the following command? rpm -q python pygtk2 gtk2 dbus-python dbus-libs Notes to self: Looking at the backtrace, it looks like an assertion failed inside frame 2 of the program's single thread inside update_refs: "Modules/gcmodule.c:242: update_refs: Assertion `gc->gc.gc_refs == (-3)' failed" whilst handling a DBus message The code in question is this line: assert(gc->gc.gc_refs == GC_REACHABLE); in this context: /* Set all gc_refs = ob_refcnt. After this, gc_refs is > 0 for all objects * in containers, and is GC_REACHABLE for all tracked gc objects not in * containers. */ static void update_refs(PyGC_Head *containers) { PyGC_Head *gc = containers->gc.gc_next; for (; gc != containers; gc = gc->gc.gc_next) { assert(gc->gc.gc_refs == GC_REACHABLE);
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.