This is a tracking bug for various retrace problems in Fedora.
Ever since bug 1885154 was resolved, I never had retrace problems again, until now: --- 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 8.5 MiB Upload successful Retrace job #190672426 started Analyzing crash data ............................... Retrace job failed Retrace failed. Try again later and if the problem persists report this issue please. [2022-12-28 17:29:02] [I] Analyzing crash data Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'NO' ('analyze_CCpp' exited with 1) --- 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 8.5 MiB Upload successful Retrace job #999291307 started Analyzing crash data .............................. Retrace job failed Retrace failed. Try again later and if the problem persists report this issue please. [2022-12-28 20:48:04] [I] Analyzing crash data Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'NO' ('analyze_CCpp' exited with 1) ============================================================================ This is repeatable, and happens for other problems (trying to report a gnome-keyring crash) too. Is this tracking bug the correct place to report this, or shall I open a new report for these problems?