Description of problem: I saw that gnome-software crashed, but abrt didn't give me the option to report it. On further investigation this turned out to be because abrt-handle-event crashed. # gdb /usr/libexec/abrt-handle-event /var/tmp/abrt/abrt-handle-event-coredump GNU gdb (GDB) Fedora 7.6.50.20130731-16.fc20 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". .. Reading symbols from /usr/libexec/abrt-handle-event...Reading symbols from /usr/lib/debug/usr/libexec/abrt-handle-event.debug...done. done. warning: core file may not match specified executable file. [New LWP 3191] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/abrt-handle-event -i -e post-create -- /var/tmp/abrt/ccpp-2013-12-'. Program terminated with signal SIGSEGV, Segmentation fault. #0 main (argc=<optimized out>, argv=0x7fff9d238d68) at abrt-handle-event.c:455 455 if (r == 0 && run_state->children_count == 0) Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace Missing separate debuginfos, use: debuginfo-install augeas-libs-1.1.0-2.fc20.x86_64 bzip2-libs-1.0.6-9.fc20.x86_64 elfutils-libelf-0.157-1.fc20.x86_64 elfutils-libs-0.157-1.fc20.x86_64 libacl-2.2.52-4.fc20.x86_64 libattr-2.4.47-3.fc20.x86_64 libcap-2.22-7.fc20.x86_64 libdb-5.3.28-1.fc20.x86_64 libffi-3.0.13-5.fc20.x86_64 libselinux-2.1.13-19.fc20.x86_64 lua-5.2.2-5.fc20.x86_64 pcre-8.33-2.fc20.1.x86_64 popt-1.16-1.fc20.x86_64 xz-libs-5.1.2-6alpha.fc20.x86_64 (gdb) bt #0 main (argc=<optimized out>, argv=0x7fff9d238d68) at abrt-handle-event.c:455 Version-Release number of selected component (if applicable): abrt-2.1.10-1.fc20.x86_64
Thank you for the report. Upstream commit c14a3bfd41ac363c523b6bcc56d53cd77220321a fixes this bug.
abrt-2.1.11-1.fc20,libreport-2.1.11-1.fc20,satyr-0.13-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/abrt-2.1.11-1.fc20,libreport-2.1.11-1.fc20,satyr-0.13-1.fc20
Package abrt-2.1.11-1.fc20, libreport-2.1.11-1.fc20, satyr-0.13-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.1.11-1.fc20 libreport-2.1.11-1.fc20 satyr-0.13-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0512/abrt-2.1.11-1.fc20,libreport-2.1.11-1.fc20,satyr-0.13-1.fc20 then log in and leave karma (feedback).
abrt-2.1.11-1.fc20, libreport-2.1.11-1.fc20, satyr-0.13-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.