search

abrt / gnome-abrt

ABRT oopses list designed according to https://live.gnome.org/Design/Apps/Oops
GNU General Public License v3.0
18 stars 21 forks source link

Failing to log to Bugzilla #322

Open Lennox84 opened 2 years ago

Lennox84 commented 2 years ago

Hi all,

I've been trying to submit multiple reports back to Bugzilla as I'm having some issues in my Fedora 36 (KDE Spin) install. I created a bugzilla API key and verified it, I also created a second one just in case the 1st one was not active or something (I did this after I had a few failed attempts). The below error message happens regardless of which API key I use.

Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla fatal: RPC failed at server. The API key you specified is invalid. Please check that you typed it correctly. abrt-action-find-bodhi-update [ERROR] Search for duplicate bugs failed: None ('analyze_BodhiUpdates' exited with 2)

I have checked that both keys exist in my Bugzilla account and neither are revoked. I'm not sure if the issues lives with abrt itself or on the Bugzilla side, let me know if you need any more info.

P.S. other reports are uploaded fine it seems - --- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' Querying server settings Preparing an archive to upload Uploading 406.8 KiB Upload successful Retrace job #927331156 started Analyzing crash data .............................................. Generating backtrace ............................. Finishing task

Thanks for your help, Bruno

andrew1044 commented 2 years ago

Question on this one.. how did you enter an API key into the app? Mine has expired and I don't see any way to provide a new key, it'll just fail repeatedly

Many thanks

Lennox84 commented 2 years ago

Wasn't aware they expire but in the web portal on Bugzilla you can create keys. This is where I created mine and I also created a 2nd (newer key) after the fails occured and tried the above but reporting still failed so I disabled/removed the new key (can't remember exactly, it was months ago now) and continued with my original as I had no reason to believe it was a problem.

Hope this helps in some way.