Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693274 - IgnoredPaths setting is ignored
Summary: IgnoredPaths setting is ignored
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 29
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-27 12:43 UTC by Jonathan Wakely
Modified: 2019-03-27 13:47 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Jonathan Wakely 2019-03-27 12:43:34 UTC
Description of problem:

abrt keeps popping up notifications about crashes in my own programs, e.g. in unit tests which are supposed to exit with SIGABRT because that's what they're testing.

I've set IgnoredPaths in /etc/abrt/plugins/CCpp.conf and it doesn't seem to help.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. gcc -x c - -o /tmp/a.out <<< 'int main() { __builtin_abort(); }'
2. /tmp/a.out

Actual results:

Notification saying "Oops! We're sorry, it looks like a problem occurred. ..."

Expected results:

The crash should not be handled by abrt because the binary is in /tmp/ and my /etc/abrt/plugins/CCpp.conf has:

IgnoredPaths = /home/jwakely/src/gcc/build*, /tmp/*

Comment 1 Jonathan Wakely 2019-03-27 13:47:07 UTC
I toggled ProcessUnpackaged in /etc/abrt/abrt-action-save-package-data.conf and adding /tmp/* to BlacklistedPaths in the same file, then restarted abrtd.service and abrt-ccpp.service, then reverted the changes to /etc/abrt/abrt-action-save-package-data.conf and restarted again. Now I can't reproduce the problem (crashes in /tmp/a.out are ignored as expected).

So the bug doesn't seem to be as simple as IgnoredPaths being completely ignored, but it doesn't always get honoured. Maybe a race condition during startup?

Note You need to log in before you can comment on or make changes to this bug.