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.
Created attachment 589423[details]
abrt screenshot
Description of problem:
abrt does not depends on libreport-plugin-bugzilla, however in requires it
Version-Release number of selected component (if applicable):
abrt-2.0.8-6.el6.x86_64
How reproducible:
I did it once and then abrt did not give me the same possibilities.
Steps to Reproduce:
1. Tried to report the bug 828666 with abrt
2. In certain step abrt asked for something like "analyse locally" or similar (I was not able to return to this point)
3. In next window it said:
Analyzing finished with exit code 127
--- Running analyze_LocalGDB ---
Analyzing coredump 'coredump'
Generating backtrace
Backtrace is generated and saved, 17003 bytes
/bin/sh: line 4: reporter-bugzilla: command not found
(exited with 127)
The screenshot is attached.
4. When tried to report the same problem once again, abrt did not gave the same option.
Actual results:
abrt failed to report
Rerun seems help, but not with the same options.
Expected results:
No problems in reporting.
Additional info:
Comment 1RHEL Program Management
2012-07-10 06:45:37 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2RHEL Program Management
2012-07-10 23:03:22 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Fixed in git:
commit c0e626795fa8f91b154338112de6fb7b4095fc79
Author: Denys Vlasenko <vda.linux>
Date: Sun Jul 29 21:54:29 2012 +0200
abrt.spec: add missing dependencies for tools we run from default cfgs
Fixed in git:
commit 993d8a66e6fa1200eea3b5549a5f47ff81e85ed4
Author: Denys Vlasenko <vda.linux>
Date: Tue Jul 31 16:50:36 2012 +0200
For RHEL, commenting out all reporter events for all types of problems
Bugfix has been verified on abrt-2.0.8-9.el6.x86_64 and libreport-2.0.9-11.el6.x86_64 packages.
Verified by
- diff of old and new config files (reporter-bugzilla and bodhi have been commented out)
- all other scripts called from event configuration files are present in default installation
- reporting actual problem without any issue
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0290.html