Bug 917268

Created attachment 704480 [details]
Screenshot of duplicated crashes in abrt-gui

Description of problem:

Every time I log in, the blueman applet crashes or raises a stacktrace in such a way that ABRT reacts to it (bug #875682, in case that's relevant). After submitting the crash so that it moves down into the "Submitted reports" list, the next occurrence of the crash will cause the ABRT systray applet to notify me about it, it will show up under "Not submitted reports", inviting me to try to submit it once again.

Version-Release number of selected component (if applicable):

abrt-2.0.20-1.fc18.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Make something crash like my blueman applet does
2. Be notified of crash, open abrt-gui, report the crash
3. Repeat the crash in #1
4. Note how you get notified about the crash again
  
Actual results:

See above.

Expected results:

ABRT should realise that all but the first crash are repeats of an already-submitted problem, and should merge the crash with that entry (i.e., increasing its "count" attribute), rather then creating a new "not submitted" entry.

Also, the ABRT systray applet should not pop up a new crash notification for every repeated occurrence. There's not much I can do about the fact that a crash happened except to report it, and considering that I have reported the problem already, the repeated notifications only serves as an annoyance.

Additional info:

ABRT is able to merge repeated crashes when there's already an entry for it present under "not submitted reports". In other words, if I reproduce a crash so that a new entry shows up as "not submitted", do nothing about it, and reproduce the crash again, I will still only have one entry under "not submitted reports". If I then proceed to inspect the actual report data, I can see that the "count" attribute has increased to 2. So the problem does not seem to be the duplicate detection algorithm itself, but that already submitted reports aren't being looked at when determining whether a new crash is a duplicate or not