Description of problem: Each time I try to report an error via abrt it complains that the username or password for Bugzilla is incorrect. Version-Release number of selected component (if applicable): abrt-0.0.8.5-1.fc12.x86_64 How reproducible: Always Steps to Reproduce: 1. Click on '!' icon, accept everything offered 2. 3. Actual results: No bug report, bad account for Bugzilla warning window Expected results: Bug gets reported Additional info: I can't find any way to register my account on Red Hat's bugzilla.
There used to be a problem with '#' being in password string, when the password was saved, in plain text, in Bugzilla.conf. Could this be the problem? Do you feel that your password has some sort of "special" chars?
Ah, I wonder if this is why it's not working from me. I don't have a #, but I do have a couple other ones that might be causing problems.
I remember I filled successfully BZ via abrt-gui, so, I believe it works. If you want to track the issu, you might wanna change your password to something simpler, just for a while, and re-check?
(I mean to change in bugzilla.redhat.com and re-check in abrt-gui.)
I changed my password, and now I'm seeing: CReporterBugzilla::Report(): CReporterBugzilla::CheckUUIDInBugzilla(): Unable to transport XML to server and get XML response back. libcurl failed to execute the HTTP POST transaction. Couldn't resolve host 'bugzilla.redhat.com' I've had a working network connection for hours...
(In reply to comment #5) > I changed my password, and now I'm seeing: > > CReporterBugzilla::Report(): CReporterBugzilla::CheckUUIDInBugzilla(): Unable > to transport XML to server and get XML response back. libcurl failed to > execute the HTTP POST transaction. Couldn't resolve host 'bugzilla.redhat.com' We've seen this bug already. It happened user when he reported bug and tried to report another one. Was this the case? Can it be possible to reveal the special char which made the problem occur?
Might have been a space.
*** This bug has been marked as a duplicate of bug 518390 ***