Hide Forgot
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
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.
Shouldn't that be bugzilla_event.conf ? abrt is affected just like sealert
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.
libreport-2.0.5-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/libreport-2.0.5-3.fc16
libreport-2.0.5-3.fc17.x86_64 contains the line EVENT=report_Bugzilla analyzer=libreport reporter-bugzilla That line does not work in abrt comment #1 line works
(In reply to comment #5) > libreport-2.0.5-3.fc17.x86_64 contains the line > > EVENT=report_Bugzilla analyzer=libreport reporter-bugzilla > > That line does not work in abrt comment #1 line works - this line should fix the problem with sealert (it works on my machine), where exactly you miss bugzilla with this patch?
(In reply to comment #6) > (In reply to comment #5) > > libreport-2.0.5-3.fc17.x86_64 contains the line > > > > EVENT=report_Bugzilla analyzer=libreport reporter-bugzilla > > > > That line does not work in abrt comment #1 line works > > - this line should fix the problem with sealert (it works on my machine), where > exactly you miss bugzilla with this patch? as I wrote, in abrt-gui Can not test sealert right now as for some reason the latest version does not capture avcs anymore 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-3.fc17.x86_64 libreport-cli-2.0.5-3.fc17.x86_64 libreport-gtk-2.0.5-3.fc17.x86_64 libreport-newt-2.0.5-3.fc17.x86_64 libreport-plugin-bugzilla-2.0.5-3.fc17.x86_64 libreport-plugin-kerneloops-2.0.5-3.fc17.x86_64 libreport-plugin-logger-2.0.5-3.fc17.x86_64 libreport-plugin-reportuploader-2.0.5-3.fc17.x86_64 libreport-python-2.0.5-3.fc17.x86_64 selinux-policy-3.10.0-11.fc17.noarch selinux-policy-targeted-3.10.0-11.fc17.noarch 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
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > libreport-2.0.5-3.fc17.x86_64 contains the line > > > > > > EVENT=report_Bugzilla analyzer=libreport reporter-bugzilla > > > > > > That line does not work in abrt comment #1 line works > > > > - this line should fix the problem with sealert (it works on my machine), where > > exactly you miss bugzilla with this patch? > > as I wrote, in abrt-gui - oh, sorry, I should have read your comment more carefully, is it for every crash detected by ABRT or only for some of them (i.e: works for python crashes, but not for kerneloops) > Can not test sealert right now as for some reason the latest version does not > capture avcs anymore > - is seapplet running?
(In reply to comment #8) > - oh, sorry, I should have read your comment more carefully, is it for every > crash detected by ABRT or only for some of them (i.e: works for python crashes, > but not for kerneloops) It works for python crashes, but not for kerneloops. Didn't test ccpp crashes
Package libreport-2.0.5-3.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreport-2.0.5-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/libreport-2.0.5-3.fc16 then log in and leave karma (feedback).
You're right, I checked the config file and bugzilla is not associated with koops: To make it work, please add following lines to /etc/libreport/events.d/koops_event.conf EVENT=report_Bugzilla analyzer=Kerneloops reporter-bugzilla
libreport-2.0.5-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/libreport-2.0.5-4.fc16
Package libreport-2.0.5-4.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreport-2.0.5-4.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/libreport-2.0.5-4.fc16 then log in and leave karma (feedback).
libreport-2.0.5-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
abrt-2.0.4-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/abrt-2.0.4-2.fc16
abrt-2.0.4-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.