Bug 582421
| Summary: | RFE: Exclude crashes in examples scripts from triggering a crash report dialog | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jef Spaleta <jspaleta> | ||||
| Component: | abrt | Assignee: | Denys Vlasenko <dvlasenk> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | anton, dvlasenk, iprikryl, jmoskovc, kklic, mnowak, npajkovs, nphilipp | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | abrt-1.1.1-1.fc12 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-06-02 18:05:33 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jef Spaleta
2010-04-14 20:54:30 UTC
Citing Mathieu's post from the fedora-devel-list thread (as I have the same issue and am too lazy to type it up ;-): --- 8< --- When I'm developing a TG2 application, I sometimes get a traceback (well, I'm not perfect :). ABRT sees the traceback, and wants me to report a bug against Paster. However, the bug is not in Paster, it's in my own code, and I know it since I'm currently developing it (Paster is used to launch TG2 applications). Would it be possible to ignore this kind of tracebacks while not ignoring legit Paster issues? --- >8 --- Just for reference that this needs a more generic solution than just ignoring programs/scripts from specific paths. Some python scripts als (ab)use tracebacks as an error reporting mechanism, son#t know how they fit into the picture... Eek: "... also (ab)use ... don't know how ..." of course. Created attachment 411773 [details]
Proposed patch
Pushed the fix to git. Now abrt.conf by default will contain: # Blacklisted executable paths (shell patterns) BlackListedPaths = /usr/share/doc/*, */example* Any other paths to add to default abrt.conf? Thanks, This should solve me immediate concern. I'm not aware of any other global paths where non functional scripts or code are allowed to reside under Fedora packaging guidelines. Anything else is probably going to be package specific and will need the more fine-grained configuration on a package-by-package basis. I've no idea if that level of complexity is really warranted. -jef (In reply to comment #4) > Pushed the fix to git. > > Now abrt.conf by default will contain: > > # Blacklisted executable paths (shell patterns) > BlackListedPaths = /usr/share/doc/*, */example* > > Any other paths to add to default abrt.conf? This for starters: /home /srv /opt /usr/local If an executable was in one of these paths, it's almost sure that it is a locally built thing or a 3rd party package. 3rd party packages are handled by "ProcessUnpackaged" option, no need to blacklist those paths. Ahh, so /home is excepted by default? Must have been introduced just lately, I remember getting alerts for private python scripts that threw around tracebacks. Nils, private python scripts should be ignored (does not matter if they reside in /home or /usr/bin). There were some improvements in that code recently. abrt-1.1.1-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/abrt-1.1.1-1.fc13 abrt-1.1.1-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.1.1-1.fc12 abrt-1.1.1-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/abrt-1.1.1-1.fc13 abrt-1.1.1-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/abrt-1.1.1-1.fc12 abrt-1.1.1-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. abrt-1.1.1-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |