Description of problem: Abrt fails to log in correctly to Bugzilla, claiming an invalid username and/or password. It does this even though I have the Bugzilla page up in Firefox and am properly logged in. Version-Release number of selected component (if applicable): abrt 1.1.18 How reproducible: 100% Steps to Reproduce: 1.Have a program crash 2.Prepare a report in abrt 3.try to send it to Bugzilla through abrt Actual results: abrt reports that it failed to log in correctly because of a username/password error. Expected results: abrt logs into Bugzilla and posts the report. Additional info: This is on a laptop using a fully updated installation of Fedora 14 and the latest version of XFCE. The exact error message is: Cannot login. Check Edit->Plugins->Bugzilla and /etc/abrt/plugins/Bugzilla.conf. Server said: RPC failed at server. The username or password you entered is not valid.
doesnt work in F15 either
In F15 neither bugzilla nor the remote trace servers work under ABRT.
are you behind the proxy?
No, no proxies. Just a direct, unfiltered connection to the Internet.
Ok, let's try something else. Set your login and passwd in /etc/abrt/plugins/Bugzilla.conf # find crash what you want to report $ abrt-cli -lf # enable debugging for xmlrpc-c $ export XMLRPC_TRACE_XML=1 # run abrt bugzilla plugin and save log abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf -d <your-crash-path> 2>&1 | tee log Open 'log' file in your favourit editor and look at the very first call. You should see something like that XML-RPC CALL: <?xml version="1.0" encoding="UTF-8"?>\r\n <methodCall>\r\n <methodName>User.login</methodName>\r\n <params>\r\n <param><value><struct>\r\n <member><name>login</name>\r\n <value><string>npajkovs</string></value></member>\r\n <member><name>password</name>\r\n <value><string>XXXXX</string></value></member>\r\n </struct></value></param>\r\n </params>\r\n </methodCall>\r\n and look if your password don't have any whitespaces. remove you password and send me the 'log'.
The issue is on my laptop, which isn't set up right now. However, I checked the file on my desktop, it doesn't have my username or password in it, and I know I've never edited /etc/abrt/plugins/Bugzilla.conf on either machine. That would explain the error message. Now, the question becomes "why doesn't abrt prompt you for username and password, either before trying to log in if they're blank, or at least after the attempt fails?" I'd guess that this wasn't caught sooner because the people testing it knew how to hand configure it and it never occurred to them that the average Linux user wouldn't. Not the worst thing they could have done, and it should be fairly easy to correct.
If you run abrt-gui, then your login and password are in gnome-keyring. abrt-gui opens gnome-keyring, reads your login and password and passes to abrt-action-bugzilla via environment variable. My goal was to know if it works from command line to bisect the problem you are heading and get more details. You can have in gnome-keyring wrong login and password (install seahorse and look directly to gnome-keyring if your login and password are ok)
Now posting from the laptop. I set the username and password as you suggested. However, abrt-cli wasn't installed, but I was able to get it with yum. Then, I tried to do the same with abrt-action-bugzilla but yum couldn't find it. Checking with whatprovides, I found that it should be plugin, not action and learned that I already had it. Alas, I can't make it work because it's just a plugin. Please advise. As far as gnome-keyring goes, I never used abrt when I used gnome, and I've now migrated all of my computers to XFCE. I still say that abrt should prompt for the username/password if it doesn't find them.
I have just now installed seahorse and verified that the password is correct, although I have no way of telling what username it's sending. When I tried to upload the crash report, it failed with the same error I always get.
Does the problem still persist?
I finally learned from a mailing list how to configure it, meaning that I've worked around the problem. However, even though I have over thirty years of computer experience I found it hard to locate the proper place to enter the username/password. And, if it can't log on, it should *prompt* you to enter what it needs, such as email programs, newsreaders and browsers have been doing for well over a decade. Just because the people who wrote the program know how to configure it doesn't mean that the average user will find it intuitive, and this UI certainly isn't.
I just needed to use abrt on my desktop after "upgrading" to F16 from F14. The username and password had been discarded during the upgrade, but abrt warned me of this and prompted me to configure the plugin. As this is what I've been asking for, I consider the issue solved and that the bug can now be closed. (I'm not closing it myself because there may be some things that have to be done to tidy up, but I don't see any reason it should stay open.)