Hide Forgot
+++ This bug was initially created as a clone of Bug #725970 +++ Since the libreport migration both abrt and sealert no longer propose to report bugs in bugzilla. That makes them all rather useless. Error reporting is required to stabolize F16 alpha $ rpm -qa setroubleshoot* abrt* libreport* |sort abrt-2.0.4-1.fc16.x86_64 abrt-addon-ccpp-2.0.4-1.fc16.x86_64 abrt-addon-kerneloops-2.0.4-1.fc16.x86_64 abrt-addon-python-2.0.4-1.fc16.x86_64 abrt-cli-2.0.4-1.fc16.x86_64 abrt-desktop-2.0.4-1.fc16.x86_64 abrt-gui-2.0.4-1.fc16.x86_64 abrt-libs-2.0.4-1.fc16.x86_64 libreport-2.0.5-2.fc16.x86_64 libreport-cli-2.0.5-2.fc16.x86_64 libreport-gtk-2.0.5-2.fc16.x86_64 libreport-newt-2.0.5-2.fc16.x86_64 libreport-plugin-bugzilla-2.0.5-2.fc16.x86_64 libreport-plugin-kerneloops-2.0.5-2.fc16.x86_64 libreport-plugin-logger-2.0.5-2.fc16.x86_64 libreport-plugin-reportuploader-2.0.5-2.fc16.x86_64 libreport-python-2.0.5-2.fc16.x86_64 setroubleshoot-3.0.38-1.fc16.x86_64 setroubleshoot-plugins-3.0.14-2.fc15.noarch setroubleshoot-server-3.0.38-1.fc16.x86_64 --- Additional comment from jmoskovc on 2011-07-27 04:31:59 EDT --- Hi, this problem will be fixed in the next update, in the meantime you can use this workaround: create a file: /etc/libreport/events.d/sealert_bz.conf and add this line: EVENT=report_Bugzilla reporter-bugzilla then it should show bugzilla target in the reporter selector. --- Additional comment from nicolas.mailhot on 2011-07-27 04:53:06 EDT --- Shouldn't that be bugzilla_event.conf ? abrt is affected just like sealert --- Additional comment from jmoskovc on 2011-07-27 05:01:15 EDT --- The name actually doesn't matter, this line will add bugzilla reporter to everything, so the proper name here would be: bugzilla_for_all.conf :) so you can easily find it and remove it, once we fix this.
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-2011-1598.html