While reporting bug into Bugzilla, I'm forced to save a password for Bugzilla account into password keyring. The should be an option to not remember passwords at all (and ask user for them each time). There can be policies forbidding password saving. Example: Send report → Select bugzilla → Bugzilla plug-in not configured → Configure Bugzilla Options → Fill in URL and user name, void password entry → Apply → Continue → Yes → Next… → Apply → Error message: Empty login or password. Please check /etc/abrt/plugins/Bugzilla.conf. If I try to configure Bugzilla plug-in from menu, I'm asked to open keyring. Becuase I do not want to store the password, I press Cancel, and I get error message Cannot save plug-in settings.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 709263 has been marked as a duplicate of this bug. ***
The bug is still in F15 in graphical interface. Command line version should be fixed already.
A "don't store passwords" checkbox was added in commit 1d4f04.
abrt-2.0.7-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/abrt-2.0.7-2.fc16
Package abrt-2.0.7-2.fc16, libreport-2.0.8-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 abrt-2.0.7-2.fc16 libreport-2.0.8-3.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16990/libreport-2.0.8-3.fc16,abrt-2.0.7-2.fc16 then log in and leave karma (feedback).
This still requires to save password into Gnome key ring before submitting report to Bugzilla. If I cancel the Gnome key ring dialogue and continue, I will get this error message: --- Running report_Bugzilla --- Empty login or password, please check your configuration (exited with 1)
There is a checkbox "Don't store passwords" which you have to check and click "OK" - clicking cancel cancels every change you did in the dialog.
It is and I confirmed the Bugzilla setting form (and if I return there now, I can see the option is on). I talk about the Gnome key ring dialogue which pops up just after that. I do not use Gnome key ring, I do not want to store a password there or initialize it or whatever the Gnome application wants (it just asks for key ring passphrase without any further explanation). So I press cancel in the key ring window, then ABRT says it could not save Bugzilla settings and few windows next I get the above mentioned ABRT error. These are detailed steps I do: (1) Double-click a not-submitted report. (2) Press Forward button in Problem description. (3) Tick on "I don't know what caused this problem", press Forward. (4) Keep smolt profile unticked, press Apply. (5) Select Bugzilla in Select reporter. (6) Error message `Wrong settings in Buzilla' appears, press Configure Bugzilla, fill in User name, keep password empty, tick Don't store passwords on, press Ok. (7) Localized modal window grabbing keyboard and focus by Gnome key ring / pinentry appears requesting passphrase to key ring (it does not say it's Gnome key ring, but what else could it be?). I press Cancel. (8) Error message "Error saving event 'report_Bugzilla' configuration to keyring" pops-up (with dummy `Unnamed window' title). The same message is printed into terminal. I dismiss the message by the only button Close. This should not happen. (9) Then the `Wrong settings in Buzilla' window from step (6) remains. I press Close. (10) I press Forward in previous window (Select reporter from (5)). (11) I press Forward in Review the data. (12) I tick the review confirmation and press Apply. (13) Next slide titled Reporting says Reporting finished with exit code 1. Lower Show log prints the error quoted in comment #7 (Empty login or password...).
This bugzilla is about a different problem - it's about not saving the password, which you described in comment#1. Now you're talking about not using the keyring at all which is not covered by this bugzilla. (note: abrt saves other credentials to keyring not just password).
What's difference between password and `other credentials'? Both of them authenticate/authorize user. I guess year ago abrt did not use key ring at all, so I could not hit it and mention it in comment #1. I my opinion, you have not solved this problem. You've just shift it into different place. If abrt uses key ring as storage for session-only credentials, it should not bother user at all and use some in-memory only storage or private key ring storage with in-memory only random passphrase (I don't know if Gnome key ring supports per-application storages).
ABRT is using the keyring since 2009-10-05. This bugzilla is really talking about the password and it's clearly stated in comment#1 if you want another changes please open another ticket.
I would say I had to have hit the key ring in time of comment #1, if nothing has changed. Nevertheless I will create new report.
(In reply to comment #13) > I would say I had to have hit the key ring in time of comment #1, if nothing > has changed. Nevertheless I will create new report. Submitted as bug #767186.
abrt-2.0.7-2.fc16, libreport-2.0.8-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.