Created attachment 459255 [details]
File: backtrace

Not sure what's wrong here,
there are many <optimized out> values in the backtrace.
Could be a Python interpreter problem or some GTK theme issue.

Changing component in case the Python maintainer
has more insight into how this could happen.

I was playing around with GTK Themes at the time that it happened, but I didn't think that was relevant. Apologies for not mentioning it.

Thank you for reporting this bug, and for mentioning the theme change: the latter seems to be significant.

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 gtk2 pygtk2 pygobject2

Looking at the backtrace, it looks like the problem occurred in thread #1, whilst attempting to log the message:
    Unable to locate theme engine in module_path: "aurora",
(as per frame #3)

Frame #13 indicates it was parsing "/home/rob/.themes/Neon/gtk-2.0/gtkrc"

The SIGSEGV happened at /usr/src/debug/Python-2.7/Python/_warnings.c:449, which is:
    PyFrameObject *f = PyThreadState_GET()->frame;

My hunch here is that we don't have the GIL at this point, and this leads to the segfault.

pygobject2 has pygobject-2.21.5/gobject/gobjectmodule.c:
  _log_func(const gchar *log_domain,

    if (G_LIKELY(Py_IsInitialized()))
    {
	PyGILState_STATE state;
	PyObject* warning = user_data;

	state = pyglib_gil_state_ensure();
	PyErr_Warn(warning, (char *) message); <<<< This is frame #3 of thread #1, where state = PyGILState_LOCKED
	pyglib_gil_state_release(state);
    } else
        g_log_default_handler(log_domain, log_level, message, user_data);

and in pygobject-2.21.5/glib/pyglib.c:
    PyGILState_STATE
    pyglib_gil_state_ensure(void)
    {
        g_return_val_if_fail (_PyGLib_API != NULL, PyGILState_LOCKED);
    
        if (!_PyGLib_API->threads_enabled)
       	    return PyGILState_LOCKED;
    
        return PyGILState_Ensure();
    }

so pygobject2 seems to have a boolean: "threads_enabled", and seems to only bother claiming the GIL if pyglib_enable_threads has been called, if I'm reading this right.

Reassigning component from "python" to "pygobject2";  hopefully the pygobject2 maintainer will be able to figure this out further or reassign as necessary.

(also looks a little like bug 551371)

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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