Description of problem: The ABRT gui will not let me report anything and keeps saying that Fedora 34 is not supported by the Retrace server. I guess it is high time it was supported because we have branched out! Version-Release number of selected component (if applicable): Problem reporting 1.3.6 on Fedora 34 How reproducible: Always Steps to Reproduce: 1. Try to report an issue via the Abrt reporting tool in Fedora 34. Actual results: Abrt will not report because the Retrace server is not set up for Fedora 34. Only local tracing is available. Expected results: Abrt will allow retracing for Fedora 34 without problems and it will be possible to report issues again.
Also reported in https://github.com/abrt/retrace-server/issues/414
*** Bug 1933447 has been marked as a duplicate of this bug. ***
Proposed as a Blocker for 34-final by Fedora user chrismurphy using the blocker tracking app because: This violates the Fedora final release criterion for default application functionality: "All applications that can be launched using the standard graphical mechanism after a default installation [...] on the x86_64 architecture must start successfully and withstand a basic functionality test." Arguably it also violates the beta and final criterion: Bug hinders execution of required Beta test plans or dramatically reduces test coverage.
Discussed during the 2021-03-01 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Beta)" and delay the classification of this bug as a Final Blocker was made as per precedent from last cycle, we only require at least one backtrace generation method (local or remote) to work per the criteria, however it's a close call whether remote retrace not working should block final, and we don't have a lot of people around to make it, so we agreed to delay the decision until it's more pressing / more folks are around to consider it. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-03-01/f34-blocker-review.2021-03-01-17.01.txt
Fixed upstream.