Red Hat Bugzilla – Bug 700252
Unable to configure Bugzilla plugin
Last modified: 2015-02-01 17:53:56 EST
Description of problem: When reporting a bug I am not given the opportunity to enter a login/password. Version-Release number of selected component (if applicable): abrt-plugin-bugzilla-2.0.1-2.fc15.x86_64 abrt-addon-kerneloops-2.0.1-2.fc15.x86_64 abrt-2.0.1-2.fc15.x86_64 abrt-debuginfo-2.0.1-2.fc15.x86_64 abrt-libs-2.0.1-2.fc15.x86_64 abrt-desktop-2.0.1-2.fc15.x86_64 abrt-addon-python-2.0.1-2.fc15.x86_64 abrt-gui-2.0.1-2.fc15.x86_64 abrt-addon-ccpp-2.0.1-2.fc15.x86_64 abrt-plugin-logger-2.0.1-2.fc15.x86_64 How reproducible: 100% Steps to Reproduce: 1.Open abrt 2.Click on an unreported crash and click Open 3.Click Forward 4.Enter a description of what you did and click Forward 5.Select 'Bugzilla' and click Configure Events 6.In the Event Configuration dialog, select Bugzilla 7.Close the dialog. 8.Click Forward. 9.Select 'I agree...' and click Forward. 10.Click Forward. Actual results: At step 6, only the Close button is sensitive. At step 10, I get: Reporting finished with exit code 1 Empty login or password, please check your configuration
Did you click "Configure Event" after selecting "Bugzilla"? (That's where you set your BZ user name and password.)
(In reply to comment #0) ... > Reporting finished with exit code 1 > Empty login or password, please check your configuration Now I see what you mean. abrt-gui knows it doesn't have your BZ credentials, but it doesn't prompt you for them.
I get an alert in the "Select reporter" dialog after checking Bugzilla: "Wrong settings detected for Bugzilla, reporting will probably fail if you continue with the current configuration. Close" abrt-2.0.1-2.fc15.i686
Created attachment 495518 [details] screenshot showing "Select reporter" dialog and BZ name and pw dialog
Created attachment 495523 [details] Screenshot-Event Configuration.png No, the "Configure Event" button is not sensitive.
(In reply to comment #5) > Created attachment 495523 [details] > Screenshot-Event Configuration.png > > No, the "Configure Event" button is not sensitive. OK, thanks. I can't reproduce this. Selecting "Local GNU Debugger" desensitizes the "Configure Event" button, but the button is sensitive when I select any of the other items. What do you have for 'libreport*'? (abrt-gui spawns bug-reporting-wizard) $ rpm -qa 'abrt*' 'libreport*' | sort abrt-2.0.1-2.fc15.x86_64 abrt-addon-ccpp-2.0.1-2.fc15.x86_64 abrt-addon-kerneloops-2.0.1-2.fc15.x86_64 abrt-addon-python-2.0.1-2.fc15.x86_64 abrt-cli-2.0.1-2.fc15.x86_64 abrt-desktop-2.0.1-2.fc15.x86_64 abrt-gui-2.0.1-2.fc15.x86_64 abrt-libs-2.0.1-2.fc15.x86_64 abrt-plugin-bugzilla-2.0.1-2.fc15.x86_64 abrt-plugin-logger-2.0.1-2.fc15.x86_64 libreport-2.0.1-2.fc15.x86_64 libreport-gtk-2.0.1-2.fc15.x86_64
libreport-2.0.1-2.fc15.x86_64 libreport-gtk-2.0.0-4.fc15.x86_64 This is because I'd done: yum --enablerepo=updates-testing update 'abrt*' and it had only pulled in libreport-2.0.1-2.fc15. Updating libreport-gtk to 2.0.1-2.fc15 fixes the problem. Perhaps libreport-gtk should have an explicit version dependency on the main libreport package.
(In reply to comment #7) > Perhaps libreport-gtk should have an explicit version dependency on the main > libreport package. - yes, you're right, going to fix this.
abrt-2.0.6-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/abrt-2.0.6-1.fc16
Package abrt-2.0.6-1.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 abrt-2.0.6-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15513 then log in and leave karma (feedback).
abrt-2.0.6-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.