If a problem occurs, ABRT pops up a notification asking me whether I want to report it or ignore it. If I click "Report", I get a new notification asking me whether I want to ignore the problem forever. I need to manually open the ABRT UI in order to report a bug. abrt-2.1.7-1.fc20.x86_64
Thank you for the report. This strange behaviour is probably caused by Shortened reporting. Please open ABRT UI -> Application menu -> ABRT Configuration and check state of a switch for Shortened reporting option.
Yes, shortened reporting was turned on.
In addition, clicking "defaults" turns shortened reporting back on.
Shortened reporting is enabled by default in GNOME. We had an requirement to make reporting really simple, therefore GNOME users reports to ABRT server only [1]. Disable Shortened reporting and Report button will report a bug to Bugzilla next time. Closing as DUPLICATE because this issues has already been reported, but please feel free to report any further bugs you find. 1: https://abrt.fedoraproject.org/ *** This bug has been marked as a duplicate of bug 994746 ***
No, it's not a duplicate of 994746 - that clearly states that there's only an ignore button. I see a report button, but clicking it does nothing.
D`oh, I though that after clicking a report button does nothing but a new notification bubble appears with an ignore button only. A report of bug #994746 has "Automatically send uReport" option enabled (bug #994746 comment #4), therefore in his case the first notification with a report button is skipped and he sees only the second bubble with an ignore button only. Well, do you still experience the problem described in comment #0 even with "Shortened reporting" disabled? Please, after disabling the option, either restart abrt-applet or log out/log in to your desktop.
Yes, that's the behaviour I see - I click report and an apparently identical dialog reappears except this time it just asks me if I want to ignore it forever. Practically speaking, that's doing nothing - there's no indication at all that anything was reported. Why do I have to restart abrt-applet? Desktop configuration options are supposed to be instant apply.
(In reply to Matthew Garrett from comment #7) > Practically speaking, that's doing nothing - there's no indication at all that > anything was reported. The second notification bubble is supposed to indicate that the problem was reported. > Why do I have to restart abrt-applet? Desktop configuration options are > supposed to be instant apply. Because abrt-applet does not yet conform to this policy.
> The second notification bubble is supposed to indicate that the problem was reported. It doesn't. > Because abrt-applet does not yet conform to this policy. Is there a bug open for that?
(In reply to Matthew Garrett from comment #9) > > Because abrt-applet does not yet conform to this policy. > > Is there a bug open for that? No, nobody has complained yet.
https://bugzilla.redhat.com/show_bug.cgi?id=1018307
(In reply to Matthew Garrett from comment #7) > Yes, that's the behaviour I see - I click report and an apparently identical > dialog reappears except this time it just asks me if I want to ignore it > forever. In the light of above, is this bug report a duplicate of bug #994746 or not? (In reply to Jakub Filak from comment #6) > Well, do you still experience the problem described in comment #0 even with > "Shortened reporting" disabled? Or, since I am not an UX expert, I would like to kindly ask you to elaborate this problem and show us a way how we can improve the reporting workflow to make it less confusing? I am not saying that I am happy with the current state, but I cannot come up with anything better.
No, it's not a duplicate. Bug #994746 refers to the situation where "Automatically file uReport" is turned on, which isn't the case here. I see a dialog that has a "report" button, but clicking on it results in no visible indication that anything has actually happened. The followup notification should tell me that a report has been filed.
(In reply to Matthew Garrett from comment #9) > > The second notification bubble is supposed to indicate that the problem was reported. > > It doesn't. For me, it says "Reported" in the headline, like this: "A Problem has been Reported A problem in the ed-1.9-1.fc19 package has been detected Ignore forever"
Wow. Ok, I guess it does say that - I managed to completely fail to notice it, since the text just uses the detected language again. "A problem in the ed-1.9.1.fc19 package has been detected and reported" might be clearer.
(In reply to Florian Weimer from comment #14) Thank you Florian! I overlooked "It doesn't". (In reply to Matthew Garrett from comment #15) Great! You are right, the message is unclear and the notification is confusing at all. I will submit a patch which will improve the message according to your idea. Thank you!
Upstream commit 47011eb9fb08653a2ddfdf7aebc0d13dc5fdd1a7 fixes this bug.
gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20
Package gnome-abrt-0.3.3-1.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-1.fc20 abrt-2.1.9-1.fc20 libreport-2.1.9-1.fc20 satyr-0.11-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 then log in and leave karma (feedback).
still happen with the updates above
(In reply to lnie from comment #20) > still happen with the updates above From my point of view, the correct fix for this bug report was to rephrase message on the second notification bubble (comment #15). If you want to always file a report in Bugzilla, turn Shortened reporting off. Please re-test and reconsider your negative karma.
I re-tested it, the result is just as comment 15. However,there is still sth supposed to be fixed:-) when the message box come up and the cursor slip in and out the box unintentionally,the box disappear immediately before the "report" clicked. I have to spend more time to reproduce the crash again if I want to report it. It's supposed to be minimized at the right bottom corner as in other fedora versions,so that the users can click on it and report the bug at anytime conveniet for them.
(In reply to lnie from comment #22) > I re-tested it, the result is just as comment 15. I hope that the notification text is clearer now. So, please reconsider karma you have given to the update. > However,there is still sth supposed to be fixed Could you please open a new bug for this new issue. It seems to me that abrt-applet does not show persistent notifications.
(In reply to Jakub Filak from comment #23) > (In reply to lnie from comment #22) > > I re-tested it, the result is just as comment 15. > > I hope that the notification text is clearer now. So, please reconsider > karma you have given to the update. I think the karma should be given with the considering of all the performance ,but not only one ,Am I right?:-) As you know,there are still some bugs need to be fixed.:( > > > However,there is still sth supposed to be fixed > > Could you please open a new bug for this new issue. It seems to me that > abrt-applet does not show persistent notifications. I opened one:#bug 1025589
(In reply to Jakub Filak from comment #23) > (In reply to lnie from comment #22) > > I re-tested it, the result is just as comment 15. > > I hope that the notification text is clearer now. So, please reconsider > karma you have given to the update. Have a bad news for you poor guy:-),there is still sth wrong with the notification text,as you know，I clicked the "reported" yesterday when the ABRT popup about the fail of the dnf come out,and the text asked in the comment 15 come out when I reproduce the crash.However,just now I yum install sth ,then I reproduce the same dnf crash,the popup ask me whether I would like to report the bug as if the bug has not been reported. BTW,the system is installed on an VM,this morning when I open the computer and then run that vm ,the popup ask me whether I would like to report the bug. > > > However,there is still sth supposed to be fixed > > Could you please open a new bug for this new issue. It seems to me that > abrt-applet does not show persistent notifications. /I opened one just now #bug 1025589
BTW,there are some testcase need to be updated list in karma page,：-） at least https://fedoraproject.org/wiki/QA:Testcase_ABRT_Actions_and_Reporters For the reason bellow: abrt-plugin-runapp is not available because the plugin was dropped 2 years ago in abrt-1.1.14 abrt-plugin-mailx has been renamed to libreport-plugin-mailx
(In reply to lnie from comment #25) > However,just now I yum install sth ,then I > reproduce the same dnf crash,the popup ask me whether I would like to report > the bug as if the bug has not been reported. Good point! abrt-applet doesn't care about the reported state of a detected problem when it receives the new problem notification and always processes the detected problem as not yet reported one. Could you please open a new bug for this.
opened one #bug 1026153 :-)
Package gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-2.fc20 abrt-2.1.9-1.fc20 libreport-2.1.9-1.fc20 satyr-0.11-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-2.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 then log in and leave karma (feedback).
gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.