Description of problem: I logged in and I saw a notification that some daemon crashed. I clicked Report. When filling out the details, I already had one of the description boxed pre-filled: "I just logged in". That was little weird, but what the hell, report! It has searched bugzilla, discovered that my report is a duplicated, and CCed me to that bug. Only after that I discovered that this all has already happened in the past. I was already CCed to that bug and my comment (exactly same) was already appended. Now my comment is there twice: https://bugzilla.redhat.com/show_bug.cgi?id=629915#c7 This is a wrong behaviour. First of all, I already reported that bug, there is no reason in notifying me that the application crashed again and I should report it again. Secondly, ABRT should not add another exactly same report to the bug. Either is should say "you already reported this bug" or it should ask "you already reported this bug, do you really want to add another comment?". The first way should be satisfactory, because I can always add more comments manually through the web browser, no reason to use ABRT for that. Version-Release number of selected component (if applicable): abrt-gui-1.1.13-2.fc13.x86_64 abrt-desktop-1.1.13-2.fc13.x86_64 abrt-libs-1.1.13-2.fc13.x86_64 abrt-plugin-bugzilla-1.1.13-2.fc13.x86_64 abrt-addon-python-1.1.13-2.fc13.x86_64 abrt-addon-ccpp-1.1.13-2.fc13.x86_64 abrt-1.1.13-2.fc13.x86_64 abrt-plugin-logger-1.1.13-2.fc13.x86_64 abrt-plugin-runapp-1.1.13-2.fc13.x86_64 abrt-addon-kerneloops-1.1.13-2.fc13.x86_64
There is more than one problem, so let me split it first: > This is a wrong behaviour. First of all, I already reported that bug, there is > no reason in notifying me that the application crashed again and I should > report it again. > I don't think it shouldn't tell user about the same crash again, but it should be probably configurable (or there should be some checkbox "don't show this crash again") - btw, both daemon and applet has a logic to prevent repeating crashes nagging user too frequently > Secondly, ABRT should not add another exactly same report to the bug. Either is > should say "you already reported this bug" or it should ask "you already > reported this bug, do you really want to add another comment?". The first way > should be satisfactory, because I can always add more comments manually through > the web browser, no reason to use ABRT for that. So do you think ABRT should check the bugzilla and refuse to report if there is the same comment or the gui should just prevent user to re-report?
(In reply to comment #1) > I don't think it shouldn't tell user about the same crash again, but it should > be probably configurable (or there should be some checkbox "don't show this > crash again") - btw, both daemon and applet has a logic to prevent repeating > crashes nagging user too frequently You might be right, it's good to know that something crashed (at least for me, but for an ordinary user?...I'm not so sure). But I think I shouldn't be asked to report this bug again, because ABRT knows I already reported it. So at least "Report" button in the notification bubble shouldn't be present (that's what I pressed in my case). And if I try to report it again (from abrt-gui), it should ask me whether I really want to do that, because I already reported it before. > So do you think ABRT should check the bugzilla and refuse to report if there is > the same comment or the gui should just prevent user to re-report? I don't think ABRT has to search bugzilla, because it already knows internally, right? I see a green marble in abrt-gui next to that item. But yes, it is also possible that when a duplicate is found and I'm already CCed to it, abrt can ask "you are already a subscriber of <link>bug XXXX</link>, do you want to add another comment with your report?". I certainly don't want to force you into some specific behavior, I just think that my duplicated comment could be avoided if just abrt asked me.
*** This bug has been marked as a duplicate of bug 567970 ***