Bug 1693282 - ProcessUnpackaged=yes is the wrong default
Summary: ProcessUnpackaged=yes is the wrong default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matej Grabovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 13:04 UTC by Jonathan Wakely
Modified: 2019-07-12 06:17 UTC (History)
11 users (show)

Fixed In Version: abrt-2.12.1-1.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-12 06:17:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jonathan Wakely 2019-03-27 13:04:54 UTC
Description of problem:

It's not helpful to ask users to report crashes in their own software, e.g. unit tests and other code that crashes as part of normal C and C++ development activities. Fedora is supposed to be an attractive platform for developers, but ships with annoying defaults.


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

abrt-2.10.10-1.fc28.x86_64
abrt-addon-ccpp-2.10.10-1.fc28.x86_64


How reproducible:

Always

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


Actual results:

abrt tries to get me to report this crash.


Expected results:

abrt doesn't interfere with typical development tasks, since the crashes can't be reported anywhere.


Additional info:

This was apparently changed by https://github.com/abrt/abrt/issues/891

I think that was a mistake.

"This would allow users to gather debugging information for system problems with third-party drivers or applications" -- we should be encouraging third-party code to be packaged as RPMs that can be installed by Fedora users, not annoying Fedora users who are writing their own code.

Comment 1 Miro Hrončok 2019-03-27 13:23:01 UTC
FWIW I agree with this - such concerns have already be reported at https://github.com/abrt/abrt/issues/891#issuecomment-73018501 but they were dismissed with a very vague argument.

Comment 2 Jonathan Wakely 2019-03-27 13:34:13 UTC
If we really think it's important to be able to capture crashes in non-RPM binaries there should be a simple way to flip the setting back and forth, for the minority of users who are experiencing such problems and want to report them. The default should be off though.

Comment 3 Miroslav Suchý 2019-05-27 08:52:38 UTC
I agree we should change the default.

Comment 4 Matej Grabovsky 2019-05-31 11:47:13 UTC
Pulls request fixing this merged: https://github.com/abrt/abrt/pull/1384

Comment 5 Fedora Update System 2019-07-03 21:18:43 UTC
FEDORA-2019-d61c2d0dd0 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d61c2d0dd0

Comment 6 Fedora Update System 2019-07-04 03:11:07 UTC
abrt-2.12.1-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d61c2d0dd0

Comment 7 Fedora Update System 2019-07-12 06:17:20 UTC
abrt-2.12.1-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


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