abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/bin/python /usr/share/yumex/yumex.pyc component: python executable: /usr/bin/python kernel: 2.6.31.6-166.fc12.i686.PAE package: python-2.6.2-2.fc12 rating: 4 reason: Process was terminated by signal 11
Thank you for the bug report. Unfortunately, without a stack trace from the crash it is impossible to determine what caused the crash. Please see http://fedoraproject.org/wiki/StackTraces for more information about getting a useful stack trace with debugging symbols. Even if you cannot reproduce this crash at will, you can prepare your system now to produce a good stack trace the next time you experience the crash. Thank you.
Created attachment 379328 [details] yumex backtrace for SEGFAULT 11 This problem occurs when yumex is used. The latest update of libgdk-x11-2.0.so.0.1800.5 has a new function "temporary_disable_extension_events". This function recursively calls itself until the stack overflows then SEGFAULT. The if ( window->impl_window == child->impl_window) test will always be TRUE as it's passed the same window object each time. The backtrace is from GDB with a breakpoint set in "temporary_disable_extension_events". I've printed out some of the locals.
could be related to this one https://bugzilla.redhat.com/show_bug.cgi?id=548827 latest gkt2 update make yumex segfault, revert to previous release of gtk2 make it work again.
*** This bug has been marked as a duplicate of bug 548849 ***