Bug 861973
Summary: | QA: Testcase ABRT Logger plugin fail | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Martin Kyral <mkyral> |
Component: | libreport | Assignee: | abrt <abrt-devel-list> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | abrt-devel-list, acook, dvlasenk, iprikryl, jfilak, jmoskovc, kklic, mlichvar, mmilata, mnowak, mtoman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-20 16:20:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Kyral
2012-10-01 13:25:51 UTC
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. |