Description of problem: ABRT's duplicate detection is broken again (see bug 758417) for a while now. Given the amount of but reports I receive, I feel it is worse than ever before. If fails to detect clear duplicates. Version-Release number of selected component (if applicable): always How reproducible: abrt-2.0.18-1.fc17 Steps to Reproduce: 1. become a package maintainer 2. maintain 150 packages 3. receive 20+ crash reports every week not easy to reproduce, I know, but that's how it is ;) Actual results: ABRT doesn't even detect obvious duplicates like bug 856622 and bug 880105 or bug 885048 and bug 866077. The latter two were even filed by the same person. Instead, ABRT suggests another bug 757641 as possible duplicate. Expected results: It should catch these obvious duplicates.
(In reply to comment #0) > Actual results: > ABRT doesn't even detect obvious duplicates like bug 856622 and bug 880105 > or bug 885048 and bug 866077. The latter two were even filed by the same > person. Sorry, I confused some numbers here. remmina: bug 836520 and bug 880105 tumbler: bug 866077, but 885048 (both reported by the same person) and bug 880721.
Please, I am drowning in but reports. :( Here is another example: https://bugzilla.redhat.com/show_bug.cgi?id=864614 - 4 obvious duplicates, all from the same reporter.
Please, please, dear ABRT developers, make it stop. I am begging on my knees I just received these two: https://bugzilla.redhat.com/show_bug.cgi?id=923906 https://bugzilla.redhat.com/show_bug.cgi?id=923907 Can a duplicate be more obvious?
(In reply to comment #4) > Please, please, dear ABRT developers, make it stop. I am begging on my knees > > I just received these two: > https://bugzilla.redhat.com/show_bug.cgi?id=923906 > https://bugzilla.redhat.com/show_bug.cgi?id=923907 > > Can a duplicate be more obvious? - ABRT actually detected these two as duplicates, they have the same hash - this seems more like a race condition, the bugs were reported in such short time period, that when the second was reported bugzilla still didn't know about the first one and there's not much we can do about this :( - I recommend you to use this service for handling abrt bugs, it's much better than bugzilla in handling duplicate reports, it's designed to handle duplicate reports and should ease your pain: https://retrace.fedoraproject.org/faf/problems/hot/*/373/*/
Thanks for your reply, Jiri. Unfortunately the retrace server doesn't really help because I have no idea how to use it. Is there any documentation available? What does "deal with duplicates" mean? Does it help me to detect duplicates and allow me to close them? Is it smart enough to figure out a bug is actually in a library my package depends on? Does it allow me forwarding bugs do the developers easily? Does it allow me to interact with the bug reporters?
(In reply to comment #6) > Thanks for your reply, Jiri. > > Unfortunately the retrace server doesn't really help because I have no idea > how to use it. Is there any documentation available? > - good point, there is no user manual and should be - the link I sent you is showing bugs for your components sorted from the most crashing one, in the left most column you can find list of bugzillas which the server considered as duplicates > What does "deal with duplicates" mean? Does it help me to detect duplicates > and allow me to close them? - yes, it periodically scan bugzilla for new abrt reports and tries to match them with other reports and continuously deduplicates > Is it smart enough to figure out a bug is actually in a library my package > depends on? - not exactly, it can tell where it crashed, but it's hard to say if the bug is in the library or the developer just misused it - but it shows a list of all components with the same crash so if there is a lot of different packages with the same crash you can easily tell, that the issues is in some library > Does it allow me forwarding bugs do the developers easily? - no, but we're working on it - right now you can only use the bz list connected with the issue and connect with the developer using bugzilla > Does it allow me to interact with the bug reporters? - no, it's based on anonymous reports which by design make contact with the report impossible - but it should be possible to add an option to contact reporters of the connected bugzillas, which is also in our TODO
Frankly speaking I think anonymous bug reports are a very bad idea, at least from a maintainer's POV. I act as a bridge between the developer and the user and I need to have a user that can respond to questions. However I can tell that https://retrace.fedoraproject.org/faf/problems/hot/ is indeed very helpful. It already helped me to fix the hottest bug (which translates to 3 bugs in bugzilla). Thanks!
(In reply to comment #8) > Frankly speaking I think anonymous bug reports are a very bad idea, at least > from a maintainer's POV. I act as a bridge between the developer and the > user and I need to have a user that can respond to questions. We offer both anonymous reporting and reporting to bugzilla for more technical users or users who are willing to respond to queries from maintainers. This combination works nicely as you have a lot of reports to generate statistics from while still having some users who will respond to queries from maintainers.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still receiving duplicates in F19 with libreport-2.1.4 and libreport-2.1.5: https://bugzilla.redhat.com/show_bug.cgi?id=973855 https://bugzilla.redhat.com/show_bug.cgi?id=980909 https://bugzilla.redhat.com/show_bug.cgi?id=981599
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Needs investigation.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.