You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
The text was updated successfully, but these errors were encountered: