Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 728130

Summary: abrt reports to BZ and then claims the bug is already reported
Product: Red Hat Enterprise Linux 6 Reporter: Michal Nowak <mnowak>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED NOTABUG QA Contact: qe-baseos-tools-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: ahecox, dfediuck, dvlasenk, gavin, kklic, mnowak, npajkovs, ohudlick
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-04 12:21:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Nowak 2011-08-04 07:13:58 UTC 
Description of problem:

Had a crash from root process, opened abrt-gui via sudo in user's session and reported the problem, however bugzilla reporter seems to misbehave since it first reports the crash and then claims the bug exists already.

--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
New bug id: 728127
Adding attachments to bug 728127
Logging out
Status: NEW https://bugzilla.redhat.com/show_bug.cgi?id=728127
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Bug is already reported: 728127
Adding new comment to bug 728127
Logging out
Status: NEW https://bugzilla.redhat.com/show_bug.cgi?id=728127

Not sure this has any relation to abrt-gui being run as a root or perhaps it's because abrt is attaching files or adding comment to an existing bug via a new connection...

Version-Release number of selected component (if applicable):

abrt-2.0.4-2.el6.x86_64
libreport-2.0.5-3.el6.x86_64
Comment 2 Jiri Moskovcak 2011-08-04 11:23:04 UTC 
Seems like bugzilla reporter was run twice. Was this with the default configuration or was it modified.
Comment 3 Michal Nowak 2011-08-04 11:56:19 UTC 
All non-XML lines from /etc/libreport:

libreport/plugins/Bugzilla.conf:# Description: Reports bugs to bugzilla
libreport/plugins/Bugzilla.conf:# Bugzilla URL
libreport/plugins/Bugzilla.conf:BugzillaURL = https://bugzilla.redhat.com/
libreport/events.d/sealert_bz.conf:EVENT=report_Bugzilla      reporter-bugzilla
libreport/events.d/ccpp_event.conf:#EVENT=report_Bugzilla analyzer=CCpp
libreport/events.d/ccpp_event.conf:#        reporter-bugzilla -c /etc/libreport/plugins/Bugzilla.conf
libreport/events.d/python_event.conf:EVENT=report_Bugzilla analyzer=Python
libreport/events.d/python_event.conf:        reporter-bugzilla -c /etc/libreport/plugins/Bugzilla.conf
libreport/events.d/bugzilla_event.conf:EVENT=report_Bugzilla analyzer=libreport reporter-bugzilla
libreport/events/report_Bugzilla.conf:Bugzilla_BugzillaURL = https://bugzilla.redhat.com
libreport/events/report_Bugzilla.conf:Bugzilla_Login =
libreport/events/report_Bugzilla.conf:Bugzilla_Password =
libreport/events/report_Bugzilla.conf:Bugzilla_SSLVerify = yes


Modified files from abrt & libreport packages:

.......T.  c /etc/abrt/abrt.conf
.M...UG..    /var/run/abrt
S.5....T.  c /etc/libreport/events.d/python_event.conf
Comment 4 Jiri Moskovcak 2011-08-04 12:06:40 UTC 
please remove: libreport/events.d/sealert_bz.conf  If you have event with the same name configured multiple times abrt will also run it multiple times.
Comment 5 Michal Nowak 2011-08-04 12:21:37 UTC 
Thanks.
Comment 6 Denys Vlasenko 2011-08-04 14:20:10 UTC 
This actually works as expected.

This configuration describes _one_ event:

EVENT=foo [cond1]
    cmd1

EVENT=foo [cond2]
    cmd2

Depending on cond1/2, cmd1 and/or cmd2 will run.