Red Hat Bugzilla – Bug 1009532
Abrt reporting bugs as a "private" mark
Last modified: 2016-11-30 19:45:11 EST
Description of problem:
Abrt reporting bugs as a "private" mark and permanent. Reporter can't even chanage "private" button because It's also disabled.
Fedora 20 user reported bugs can be also private and making problem. Because no one can't even see it also without report we can't determine fedora 20 problems.
The bugs I reported and checked "private ;
If It's happened again. I will post every bugs to here.
Another bug marked "private" ;
Thank you for the bug report! It looks like that abrt incorrectly interprets configuration options. abrt thinks that you've requested to create a bug report with restricted access because of possibly sensitive data were detected and along with that request you wanted abrt to remember your decision.
Could you please run the following command and submit the output here:
$ grep ABRT_CREATE_PRIVATE_TICKET $HOME/.config/abrt/settings/report-gtk.conf
Result was coming nothing all output just this 2 lines.
thunderbirdtr@heisenbug settings$ cat report-gtk.conf
abrt_analyze_smart_ask_perform_local_analysis = "yes"
abrt_analyze_smart_ask_upload_coredump = "yes"
I am sorry, but I am not able to reproduce this bug (see bug #1011000). ABRT does not mark the report as private unless I explicitly require it. It means that I click Yes button on the dialogue asking me if I want to restrict access to the report. Are you sure that you click No button on that dialogue? It would be nice if you could upload a demonstrative video .
I select "no" for restriction and done now It's working. no need to screencast.
Per comment #5, setting this report to CLOSED:NOTABUG.
abrt shouldn't have the ability to mark bugs private.
I refuse to work all bugs marked private (I can't forward them upstream) and close them as not a bug.
I have closed dozens of reports due to this issue.
Please remove this option altogether or add all my packages to the abrt blacklist!!!
I agree that abrt should much more carefully examine the data before offering users to create a private report. We already have a bug report opened for this issue (bug #1009730). I would close this particular bug report as NOTABUG, if you don't mind.
(In reply to Jakub Filak from comment #8)
> I agree that abrt should much more carefully examine the data before
> offering users to create a private report. We already have a bug report
> opened for this issue (bug #1009730). I would close this particular bug
> report as NOTABUG, if you don't mind.