Created attachment 689750 [details] abrt popup Description of problem: Seeing Open and Show buttons in the popup annoys me every time I see it. There is no clear difference between those two words. A general user has no idea what two different actions are hidden behind it. Neither do I, because I never remember which one of those freaking buttons do which action. Either you need to provide clear names, or remove one of the buttons. Version-Release number of selected component (if applicable): abrt-retrace-client-2.0.20-1.fc18.x86_64 abrt-addon-kerneloops-2.0.20-1.fc18.x86_64 abrt-plugin-bodhi-2.0.20-1.fc18.x86_64 abrt-2.0.20-1.fc18.x86_64 abrt-dbus-2.0.20-1.fc18.x86_64 abrt-gui-2.0.20-1.fc18.x86_64 abrt-addon-vmcore-2.0.20-1.fc18.x86_64 abrt-libs-2.0.20-1.fc18.x86_64 abrt-addon-python-2.0.20-1.fc18.x86_64 abrt-addon-xorg-2.0.20-1.fc18.x86_64 abrt-addon-ccpp-2.0.20-1.fc18.x86_64 abrt-desktop-2.0.20-1.fc18.x86_64
Thank you for the bug report. Description of the buttons: Open -> opens a GUI app with all detected problems (old behaviour) Show -> shows a web page containing details of the detected problem (new feature add few releases back; opens an URL in a browser) Well, to be honest, I'm not able to work out short and clear names. I really appreciate any idea. Thank you in advance.
Well I think the mistake is to provide 4 different actions in a single popup: [Close], [Ignore], [Open] and [Show]. It's not clear whether [Ignore] and [Close] is the same, i.e. whether [Ignore] means 'ignore now' (==close) or 'ignore in future'(==don't show again). I have already described the confusion between [Open] and [Show] in comment #0. If [Ignore] and [Close] is the same, then ideally there should be only a single button: > [Open report] The user can close the popup or open the report. If [Ignore] means 'ignore forever', there would be two buttons: > [Ignore problem in future] [Open report] After clicking on [Open report], a window should be displayed with a summary of the problem (traceback), clickable hyperlink that opens the retrace server url, a button to report this problem, and a button to ignore this problem in the future. That's what I imagine as an intuitive UI. Currently the main ABRT window is opened instead, and I have to try very hard to find the new issue in that window, which I find very unintuitive. Also the [Show] button is very unintuitive, because it opens up a web browser, but I have no idea whether my crash was counted or not when I chose to open the web report. Should I open ABRT manually and report the problem again? I just have not the slightest clue how it should work. I understand that re-doing the GUI to bit more friendly takes a lot of time. I think the current short-term solution could be: > [Ignore problem in future] [Open ABRT] The [Open ABRT] actions opens up the main ABRT window. The web report could be shown after selecting the problem and using "Problem -> Show web report" menu item. General users don't need that functionality, why should that be part of the popup anyway? Menu item is enough.
Fixed in git: commit b8b7b2140d1927e8d59b689880efc64624d4d723 Author: Jakub Filak <jfilak> Date: Tue Feb 26 12:51:11 2013 +0100 applet: remove confusing "Show" button - the button was opening problem's web page - since applet opens the gui with preseleceted problem and the gui provides clickable links to problem's pages, Show button is no more necessary - related to rhbz#905412 Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Jiri Moskovcak <jmoskovc> commit 491e05edc2782c27d7662a8ccc5e418d7452dcbc Author: Jakub Filak <jfilak> Date: Thu Mar 14 16:12:00 2013 +0100 applet: mark problems as ignored and don't notify ignored problems - the ignore button just closed a notify bubble until this patch - from now the ignore button marks a problem as ignored in the future - closes rhbz#909968 and rhbz#905412 Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Denys Vlasenko <dvlasenk>
abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18
Package abrt-2.1.2-1.fc18, libreport-2.1.2-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.1.2-1.fc18 libreport-2.1.2-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4176/abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18 then log in and leave karma (feedback).
Package abrt-2.1.2-2.fc18, libreport-2.1.2-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.1.2-2.fc18 libreport-2.1.2-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4176/abrt-2.1.2-2.fc18,libreport-2.1.2-2.fc18 then log in and leave karma (feedback).
abrt-2.1.2-2.fc18, libreport-2.1.2-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.