Description of problem: When reporting problem to the Logger according the https://fedoraproject.org/wiki/QA:Testcase_ABRT_Logger_plugin test case, the report is not written to the log for the first time for a bug. A 'post-create' is invoked instead. Repeating the steps (6), 7, 9 for the same problem leads to the expected results. Version-Release number of selected component (if applicable): abrt-2.0.13-1.fc18 How reproducible: Always Steps to Reproduce: 1. Follow the test scenario 2. Repeat steps (6), 7, 9 Actual results: 1. The log is not created (if not present). No data written in the log. 2. The log is created (if not present). Crash data written. Expected results: 1. The log is created (if not present). Crash data written. 2. Crash data written. Additional info:
I can reproduce this issue on my system as well. The first time through the test procedure, ABRT performs a post-create not the 'logger' as requested on the first screens.
I am also seeing the exact same issue when following this basic procedure and trying to initially report via Bugzilla (https://fedoraproject.org/wiki/QA:Testcase_ABRT_Bugzilla_plugin?rd=QA:Testcase_ABRT_Bugzilla) and Mailx (https://fedoraproject.org/wiki/QA:Testcase_ABRT_Mailx_plugin?rd=QA:Testcase_ABRT_Mailx), namely, abrt-gui ignores that the Bugzilla or Mailx reporting selection initially and defaults to 'post-create'. The next time through the same bug accepts the Bugzilla or Mailx selection.
commit 4b683ff098f65057e31b7f8203717896dc331d2d Author: Jakub Filak <jfilak> Date: Tue Oct 9 16:04:25 2012 +0200 don't update the selected event while processing it - If user wrote a comment or added a file, the selected event was updated to the post-create event - closes rhbz#861973 Signed-off-by: Jakub Filak <jfilak>
abrt-2.0.15-1.fc17, libreport-2.0.16-1.fc17, btparser-0.20-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.15-1.fc17,libreport-2.0.16-1.fc17,btparser-0.20-1.fc17
Package abrt-2.0.15-1.fc17, libreport-2.0.16-1.fc17, btparser-0.20-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.15-1.fc17 libreport-2.0.16-1.fc17 btparser-0.20-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15968/abrt-2.0.15-1.fc17,libreport-2.0.16-1.fc17,btparser-0.20-1.fc17 then log in and leave karma (feedback).
Package abrt-2.0.16-1.fc17, libreport-2.0.16-1.fc17, btparser-0.20-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.16-1.fc17 libreport-2.0.16-1.fc17 btparser-0.20-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15968/abrt-2.0.16-1.fc17,libreport-2.0.16-1.fc17,btparser-0.20-1.fc17 then log in and leave karma (feedback).
abrt-2.0.16-1.fc17, libreport-2.0.16-1.fc17, btparser-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.