Description of problem: ABRT is used to catch crashes on Fedora, that does include Firefox crashes. But these crashes are reported by Firefox itself to the upstream project, so there is no need to have ABRT report them to bugzilla. Version-Release number of selected component (if applicable): How reproducible: start firefox and crash it... Steps to Reproduce: 1. start firefox 2. send SIGSEGV to it 3. see that firefox catched the crash and that ABRT will do so too Actual results: ABRT sends ureport and opens bugzilla ticket Expected results: ABRT does not catch firefox related crashes Additional info: Please "blacklist" firefox related crashes as we negotiated to to so with Martin Stransky (our firefox maintainer).
Update /usr/lib/xulrunner-*/plugin-container to /usr/lib(64)/firefox/plugin-container in /etc/abrt/abrt-action-save-package-data.conf
I'd say we need automated anonymous reports frpm Firefox, which should be explored later. We don't need a bug for every crash, just for the most important, frequent ones.
I've opened a pull request for this issue: https://github.com/abrt/abrt/pull/837
abrt-2.2.2-2.fc20,libreport-2.2.3-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/abrt-2.2.2-2.fc20,libreport-2.2.3-3.fc20
Package abrt-2.2.2-2.fc20, libreport-2.2.3-3.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.2.2-2.fc20 libreport-2.2.3-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2191/abrt-2.2.2-2.fc20,libreport-2.2.3-3.fc20 then log in and leave karma (feedback).
abrt-2.2.2-2.fc20, libreport-2.2.3-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.