abrt 1.0.8 detected a crash.
Attached file: backtrace
cmdline: /usr/bin/python ./session-emacs-daemon -n
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Created attachment 404964 [details]
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 libgnome gnome-python2-gnome
Looking at the backtrace, it looks like the problem occurred in the program's single thread in frame #5 in gnome_program_module_addtolist, as called in frame #9 by the Python bindings to libgnome (in the gnome-python2-gnome RPM).
Reassigning component from "python" to "gnome-python2"; hopefully the gnome-python2 maintainer will be able to figure this out further or reassign as necessary.
It may be a bug in libgnome, or in the script. (Arguably if the script is calling into libgnome in an unexpected way, the bindings should protect against that, though I'm not sure if that's what's happening)
I regret to say that I do not know how to reproduce the problem. The Python script that was running when it happened has even changed since then, so I am just not able to give more information than what appeared in the original failure report. :-(
Thanks for responding.
I'm glad it's no longer crashing, but without a reproducer, it's going to be hard to address this further, so I'm going to close this report out with the "not enough info" status.
If it happens again, feel free to reopen this bug.
Thanks again for the information.