When an application includes locked memory regions, ABRT refuses to report crashes to avoid leaking private information. This makes a lot of sense as a default, but it's a real problem to help fixing applications. For example, Evolution always includes locked memory regions, which means I'm never able to report any crash in it. Yet, I'm willing to take the risk and review the sent data carefully to check that no password is leaked. It would be nice to provide a check box "Yes, I know what I'm doing" to allow that. Else, many applications will continue crashing without anybody report being filed.
Thank you for the report. We are already tracking a similar request in upstream: https://github.com/abrt/libreport/issues/435 While we would love to fix it and we know how to do that technically, we are not sure how to make this feature available for our users in GUI. Alan, can you please help us with adding this advanced user feature to gnome-abrt?
Created attachment 1186676 [details] A screenshot of gnome-abrt refusing to report a crash with locked memory This is what gnome-abrt looks like when a problem that cannot be reported is selected. We need to allow our users to get rid of the warning and re-enable the Report button. There is no need to touch any other project than gnome-abrt - the "not-reportable" check is enforced only by the application itself. We are going to introduce a new command line argument "--unsafe" to ABRT command line interfaces (abrt, abrt-cli). There are few other warnings that makes a problem "not-reportable". For example: - "A kernel problem occurred, but your kernel has been tainted (flags:%s). Kernel maintainers are unable to diagnose tainted reports." - "A kernel problem occurred because of broken BIOS. Unfortunately, such problems are not fixable by kernel maintainers." - "A kernel problem occurred because of broken BIOS. Unfortunately, such problems are not fixable by kernel maintainers." - "The problem data are incomplete. This usually happens when a problem is detected while computer is shutting down or user is logging out. In order to provide valuable problem reports, ABRT will not allow you to submit this problem. If you have time and want to help the developers in their effort to sort out this problem, please contact them directly." I have decided to call the new command line argument "unsafe" because - either the reporter can leak some private data - or the reporter could be facing anger from maintainers when they get to the report
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.