Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it possible to overcome the not-reportable check #435

Open
jfilak opened this issue Apr 27, 2016 · 4 comments
Open

Make it possible to overcome the not-reportable check #435

jfilak opened this issue Apr 27, 2016 · 4 comments

Comments

@jfilak
Copy link
Contributor

jfilak commented Apr 27, 2016

I know that it is possible to do it right now by enabling e-mail report work-flow which can be use to report "not-reportable" problems, but I believe users should be allowed to report "not -reportable" problems to any bug report destination on their own risk -> it must be clearly stated in the bug report that the reporter forced libreport to file the report.

@sdodson
Copy link

sdodson commented Apr 27, 2016

/sub

@Jonrysh
Copy link

Jonrysh commented Jul 31, 2016

To jfilak: I need to have abrt report an error in evolution, which "locks memory". Can you clarify your comment about "enabling e-mail report work-flow" to someone who is not familiar with abrt's details?

@jfilak
Copy link
Contributor Author

jfilak commented Aug 1, 2016

I am sorry, my first comment is incorrect - it is not possible to report ireportable problems via any workflow, because the check is performed by the reporting tools.

Please remove the "not-reportable" file from the data directory (gnome-abrt -> Details -> data_directory) to make the problem "reportable" and report it to Bugzilla as usually.

@mhabrnal
Copy link
Contributor

mhabrnal commented Aug 2, 2016

Will be done by issue abrt/abrt#1166
We add a parameter for unsafe reporting which allows report not-reportable problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants