I tried to submit a report from abrt for several different crashes. It asks to copy the coredump to my home directory and I accept. For known issues, it returns quickly with that information. But if it's not known, it says it's "Preparing an archive to upload", but it never gets past that. I eventually have to stop it and the report gets moved to the submitted list. I've tried sending it again from there with the same result. Here is the log: --- Running report_uReport --- (exited with 0) --- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' Querying server settings Preparing an archive to upload Further investigation indicates that /usr/libexec/abrt-handle-event is stuck waiting for output from report-gtk. Here's the stack: #7 0x4a4bb82f in fgets () from /lib/libc.so.6 #8 0x4921c2d2 in run_event_stdio_ask_yes_no () from /lib/libreport.so.0 #9 0x4921d2de in consume_event_command_output () from /lib/libreport.so.0 #10 0x4921d4d0 in run_event_on_dir_name () from /lib/libreport.so.0 #11 0x08048e3b in main ()
*** Bug 873217 has been marked as a duplicate of this bug. ***
Fixed in git: commit d6b6a3bc0df05267989758644d626e6c3d63ad97 Author: Jakub Filak <jfilak> Date: Tue Nov 6 13:47:41 2012 +0100 abrt-handle-event: forward event process requests to parent
Are you going to do a build with that change soon? I have several crashes I would like to send.
Will this get backported to F17 too? I have the same problem here on F17.
abrt-2.0.19-1.fc17,libreport-2.0.19-1.fc17,btparser-0.23-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.19-1.fc17,libreport-2.0.19-1.fc17,btparser-0.23-1.fc17
Or if you're willing to help us with testing or don't want to wait for official updates, you can use the nightly builds repo: http://rmarko.fedorapeople.org/
Package abrt-2.0.19-1.fc17, libreport-2.0.19-1.fc17, btparser-0.23-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.19-1.fc17 libreport-2.0.19-1.fc17 btparser-0.23-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18329/abrt-2.0.19-1.fc17,libreport-2.0.19-1.fc17,btparser-0.23-1.fc17 then log in and leave karma (feedback).
abrt-2.0.19-1.fc18,libreport-2.0.19-1.fc18,btparser-0.23-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/abrt-2.0.19-1.fc18,libreport-2.0.19-1.fc18,btparser-0.23-1.fc18
btparser-0.23-1.fc18, abrt-2.0.19-2.fc18, libreport-2.0.19-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
abrt-2.0.20-1.fc17, btparser-0.24-1.fc17, libreport-2.0.20-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.20-1.fc17,btparser-0.24-1.fc17,libreport-2.0.20-1.fc17
abrt-2.0.20-1.fc17, btparser-0.24-1.fc17, libreport-2.0.20-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.