This is unfortunate for a beta edition, but I don't find a criteria where it could fit

BetaFE +1

This should technically be a blocker however, I will like to see this getting fixed in Final and have a FE for now

BetaFE +1
FinalBlocker +1

BetaFE +1
FinalBlocker +1

This is a final blocker per criterion:
https://pagure.io/fedora-qa/blocker-review/issue/75

About BetaBlocker, I'd like to have it as one, but I'm not sure we can say it "reduces test coverage":
https://bugzilla.redhat.com/show_bug.cgi?id=1878317#c4

Also please note I'm voting for a blocker with a requirement that ABRT must be able to report a bug. Whether it allows a local tracing or remote tracing is, I believe, an implementation detail. But at least one option must work (and the other option must not be very prominently broken, that would make it seem as a basic functionality).

AGREED AcceptedBetaBlocker

Discussed during the 2020-09-14 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker" was made on the grounds that it "hinders execution of required Beta test plans or dramatically reduces test coverage", like the other similar bugs. We will sort out which bugs do and don't exist with which updates after the meeting.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-09-14/f33-blocker-review.2020-09-14-16.01.txt

The following votes have been closed:

• Accepted BetaBlocker (+0, 0, -0)

FinalBlocker +1
I believe that ABRT is really important, especially near launch. We won't be able to fix anything if reports can't come through.

FinalBlocker +1
It is very disturbing for new users who experience bugs or crashed and then find out they are not able to report the bug because of another pending bug...