Reporting Crash, API Key Banned?

I’ve noticed the last few times I’ve tried to report a crash, the “Processing failed” but didn’t check why until just now and found this line:

The API key you specified has been banned by an admin.","error":true,"code":32000

I have no idea why any of that would be true; that is, why an API key I’ve never set up or used has been banned by anyone.

Any help? Thanks, in advance!

Yeah, that’s really annoying. You have to make sure you have an active bugzilla API key before ABRT can create a bug. Login to https://bugzilla.redhat.com/, choose the drop-down menu on your name in the upper right-hand corner, and choose Preferences. You should see a horizontal list of categories. The fifth from the left is API Keys; choose that. From here you can manage your API keys, or create a new one if you don’t have any.

Once you have an API key, in ABRT, choose the hamburger menu in the upper right, and select Preferences. In the popup box, choose the Configure button in the lower right. That will pop up another box, with “uReport” and “Bugzilla” on the left. Choose Bugzilla. There is a box there where you can paste your bugzilla API key.

There you go. How to make ABRT work in only 42 easy steps!

4 Likes

Wow… That’s not very user-friendly.

Unfortunately, I can’t login to the site because it throws a “400 error” every time, even after I flushed the cache and tried several browsers.

Ugh.

I got a 400 error yesterday when trying to log in to discussion.fedora.org
I closed the tab and then went back to discussion.fedora.org in a new tab and it logged me straight in.

Unfortunately, I had tried that; however, I just tried logging in with my Red Hat credentials and not my Fedora ones and that worked.

The API listed itself as banned, but provided no reason. Who knows.

Thanks, Jerry James for the help!

41 steps would fit better to the actual Fedora Release :grin:

1 Like

That’s by design:

You should also get emails warning you before the keys expire, but unless the key name included ABRT or similar it may not have been obvious what the emails were for.

Interesting. Although I don’t recall receiving any such emails, you’re right that I would have likely just dismissed them if they weren’t very informative or if I didn’t realize what they were telling me. Thanks for those insights, Thomas…

1 Like

And now I can’t seem to report any bugs because it dies with this, regardless of if I check or don’t check “Restrict access to report:”

Creating a new bug...
Failed to create bug.
Server says: 401 Unauthorized
{"documentation":"https://bugzilla.redhat.com/docs/en/html/api/index.html","error":true,"message":"Sorry, but you are not allowed to (un)mark comments or attachments as private.","code":113}
('report_Bugzilla' exited with 1)

It’s almost like they don’t want me to report issues… Ugh.

You could report a bug about the API via the Bugzilla website.

The ironic inception of reporting a bug about a bug reporting app is beautiful.

3 Likes

Do you insert the API Key ID? It’s the only thing I see for API keys.

Yeah, that’s already there. The bug I reported to Bugzilla about it is, so far, untouched.

Okay. Because I attempted to enter my API Key ID number and I still kept getting the 400 error when trying to report a bug, that the key was banned, even though it is a brand new key and is not banned.
Reporting a bug should not be this difficult.

1 Like

Sadly, my “new” error is a “401” error.