Description of problem: abrt's duplicate detect seems to be broken again. I receive a lot of duplicates and I just received two bug reports with an identical hash Version-Release number of selected component (if applicable): libreport version: 2.0.7 abrt_version: 2.0.6 How reproducible: don't know Steps to Reproduce: 1. don't know. Actual results: bug 758394 and bug 758395 are the same and have the same hash value of 86477caa0830e4561445305f294dce8678a479e9. Expected results: bug 758395 should be detected as a duplicate of bug 758394 Additional info: Could that be a race condition of clicking the submit button twice?
Another example: bug 758379 is a duplicate of bug 754585. Both have the same hash and this definitely is no race condition.
hmm, it starts with bugzilla's update; let's ask bugzilla's guys, because we didn't change the code. Any ideas what's going on?
I'm pretty sure this is meant to be filed against the Bugzilla product, not the bugzilla component of Fedora.
Raising priority as this results in tons of duplicate bugs filed every day. For the record: *Some* older bugs are still correctly identified as dupes, but new ones are not.
I have fix for that in my local git repo. Maybe push it into stable?
Do you still experience this bug?
Only sometimes, when the code has changed in the mean time. e.g. line numbers are no longer the same but the crash function and the crash itself is still the same. I guess there is not much we can do about this, so feel free to close this bug. It has already improved a lot.