I just hit a crash in virt-manager in latest Fedora 20. When I open it in abrt, I see: "Reported ABRT Server [hyperlink] This problem hasn't been reported to Bugzilla yet. Our developers may need more information to fix the problem. Please consider reporting it - you may help them. Thank you." When I click the ABRT Server hyperlink, I get: https://retrace.fedoraproject.org/faf/reports/239689/ which is a proper FAF report, and correctly reports that there is no associated BZ bug. But if I click the "Report" button in abrt - top right, next to Delete - the usual 'report' process window opens, and I see: Processing finished. > Show log When I expand the "Show log" expander, I get: --- Running report_uReport --- A bug was already filed about this problem: ABRT Server: URL=https://retrace.fedoraproject.org/faf/reports/bthash/b6ba3b2a1855727a087ee0c5f21bf8aa548854d8 That URL is 404. So it seems like I can't report the problem via abrt. Will attach a tarball of the report directory.
Created attachment 811742 [details] Tarball of the unreportable crash
Thank you for the report. A pull request [1] is supposed to fix this bug. [1] : https://github.com/abrt/abrt/pull/730
Upstream commit 783e0e1248a4bad3882135adf3eb69e9429b8ec4 fixes this bug.
Could we please have builds with the fix ASAP? This is hindering me from reporting bugs that should really be getting reported...thanks!
(In reply to Adam Williamson from comment #4) > Could we please have builds with the fix ASAP? This is hindering me from > reporting bugs that should really be getting reported...thanks! Sure, we are working on the release. You can work around this bug by deleting ureports_counter file from dump directory. gnome-abrt > Right click on the reported problem in list -> Open directory -> delete ureports_counter
gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20
Package gnome-abrt-0.3.3-1.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-1.fc20 abrt-2.1.9-1.fc20 libreport-2.1.9-1.fc20 satyr-0.11-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 then log in and leave karma (feedback).
Package gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-2.fc20 abrt-2.1.9-1.fc20 libreport-2.1.9-1.fc20 satyr-0.11-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-2.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 then log in and leave karma (feedback).
gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.