Description of problem: Ordinarily, a user will want to get a problem report when a packaged application crashes. However, if I'm a developer working on a loadable module for a packaged application (e.g. gedit, GTK, python, etc.), then I don't want ABRT to pick up those crashes, because it stuffs ABRT with a bunch of reports that will never go upstream (which makes ABRT less useful) and is kind of annoying (since it's a flurry of "XYZ crashed" notifications on the desktop) So, I'd like to be able to tell ABRT to ignore a particular execution of an application, even if the crash is in a packaged app that I'd want to see crash reports on otherwise. After discussions with jmoskovc on #fedora, I'd like to propose making these environment variables standard: ABRT_IGNORE_ALL=1 ABRT_IGNORE_PYTHON=1 ABRT_IGNORE_CCPP=1 So, adding a events.d file which deletes events with those environment vars set: --- # Ignore any crashes when the app was run w/ ABRT_IGNORE_ALL=1 in its # environment EVENT=post-create environ~="ABRT_IGNORE_ALL=1" rm . # Ignore C/C++-based crashes with ABRT_IGNORE_CCPP EVENT=post-create analyzer=CCpp environ~="ABRT_IGNORE_CCPP=1" rm . # And ignore Python crashes with ABRT_IGNORE_PYTHON EVENT=post-create analyzer=Python environ~="ABRT_IGNORE_PYTHON=1" rm . ---
I propose to add even: ABRT_IGNORE=<some regexp>
Sounds good to me ( my guys will just do =.* :-) ). Is that stuff accessible from inside the config file?
Yes, it can be implemented in .config files, no need to change C code. Fixed in git: commit 86c6d0de1dde119115930fec72232aff628bc9f8 Author: Denys Vlasenko <vda.linux> Date: Fri Oct 5 13:55:55 2012 +0200 Make it possible for developer to disable crash processing for specific apps
abrt-2.0.15-1.fc17,libreport-2.0.16-1.fc17,btparser-0.20-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.15-1.fc17,libreport-2.0.16-1.fc17,btparser-0.20-1.fc17
Package abrt-2.0.15-1.fc17, libreport-2.0.16-1.fc17, btparser-0.20-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.15-1.fc17 libreport-2.0.16-1.fc17 btparser-0.20-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15968/abrt-2.0.15-1.fc17,libreport-2.0.16-1.fc17,btparser-0.20-1.fc17 then log in and leave karma (feedback).
Package abrt-2.0.16-1.fc17, libreport-2.0.16-1.fc17, btparser-0.20-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.16-1.fc17 libreport-2.0.16-1.fc17 btparser-0.20-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15968/abrt-2.0.16-1.fc17,libreport-2.0.16-1.fc17,btparser-0.20-1.fc17 then log in and leave karma (feedback).
abrt-2.0.16-1.fc17, libreport-2.0.16-1.fc17, btparser-0.20-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.