Description of problem: libreport files bugs before determining if they already exist, resulting in duplicate bug reports; user is asked if they still want to file a new bug, but the new bug has already been filed. Version-Release number of selected component (if applicable): Fedora-Live-Desktop-x86_64-19-Beta-TC1-1.iso libreport-2.1.3-3.fc19 This has been applied prior to running the installer: python-meh-0.24-1.fc19 (from updates-testing) How reproducible: Unknown. Steps to Reproduce: 1. Cause a crash for an already filed bug. 2. Have libreport submit the captured bug, as you would not already knowing the bug is a duplicate. Actual results: 1. libreport files the bug, even though one already exists. 2. libreport informs the user the bug is already reported, displays the NEW bug ID. 3. libreport asks the user if they still want to file a new bug, even thought it's already been filed. Expected results: It should list the earlier bug ID, not the just filed new bug ID. And it shouldn't file a new bug unless the user clicks the Yes button to file a new bug. Additional info: The bug it filed, even though I didn't ask it to, and then said was a duplicate: https://bugzilla.redhat.com/show_bug.cgi?id=958956 The actual duplicate it should have listed: https://bugzilla.redhat.com/show_bug.cgi?id=958897
Fixed in upstream git. libreport commit 4220b461b18a141d137f184c200753bd84b6c873 Author: Jakub Filak <jfilak> Date: Thu May 16 17:52:31 2013 +0200 anaconda: add proper configuration Related to rhbz#958961 Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Richard Marko <rmarko> ABRT commit e04c69f2d4435496b34dc8242ea1d4f2eba84c08 Author: Jakub Filak <jfilak> Date: Thu May 16 17:52:38 2013 +0200 python: disable events in collision with anaconda Closes rhbz#958961 Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Richard Marko <rmarko>
abrt-2.1.5-1.fc19,libreport-2.1.5-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/abrt-2.1.5-1.fc19,libreport-2.1.5-1.fc19
Package abrt-2.1.5-1.fc19, libreport-2.1.5-1.fc19: * should fix your issue, * was pushed to the Fedora 19 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.5-1.fc19 libreport-2.1.5-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10886/abrt-2.1.5-1.fc19,libreport-2.1.5-1.fc19 then log in and leave karma (feedback).
abrt-2.1.5-1.fc19, libreport-2.1.5-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.