SUMMARY The "Problem Reporting" (ABRT) utility hangs indefinitely during the analyze_CCpp phase when generating a backtrace for C/C++ crashes, providing no timeout or progress feedback.

DESCRIPTION When attempting to report a crash (e.g., maliit-keyboard or slack), the ABRT workflow reaches the "Generating backtrace" step and stops responding. Terminal output shows the process reaches analyze_CCpp but never completes. Manual intervention (Ctrl+C) is required to exit. This prevents users from submitting high-quality bug reports with stack traces.

STEPS TO REPRODUCE

Open "Problem Reporting" (abrt-gui).

Select a recent C/C++ crash.

Click "Report".

Observe the process stalling at the backtrace generation stage.

OBSERVED RESULT The UI remains on "Generating backtrace" indefinitely. No disk or network activity is clearly indicated in the UI, and no error message is produced.

EXPECTED RESULT ABRT should either:

Complete the backtrace in a reasonable timeframe.

Provide a progress bar for debuginfo downloads.

Timeout with an error message allowing the user to submit the "raw" report without the backtrace.

ADDITIONAL INFO (TERMINAL LOG)

Plaintext
--- Running report_uReport ---
('report_uReport' completed successfully)
--- Running analyze_CCpp ---
Generating backtrace
[Process hangs here]
SOFTWARE/OS VERSIONS

OS: Fedora 43 KDE Workstation

Package: abrt-desktop / abrt-gui

Version: (You can get this by running rpm -q abrt)