Red Hat Bugzilla – Bug 1266959
Abrt-addon-ccpp tells me "Reporting disabled because the backtrace is unusable" on most crashes
Last modified: 2016-07-21 09:54:44 EDT
Description of problem:
On most crashes I see on a F22 machine I get this error message when reporting the crash:
Reporting disabled because the backtrace is unusable
But there are no errors in the log (or event_log file). Just content like this:
--- Running report_uReport ---
('report_uReport' completed successfully)
--- 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). 'NO'
Analyzing coredump 'coredump'
Alle Debuginfo-Dateien sind vorhanden
Backtrace is generated and saved, 17022 bytes
Looking for similar problems in bugzilla
Searching for updates
No updates for this package found
Version-Release number of selected component (if applicable):
Very often on this machine. Maybe 60%…80% of all crashes.
Steps to Reproduce:
1. Wait for crash to happen
2. When gnome-abrt notifies you, open gnome-abrt and press "Report"
3. Wait for report to finish
Reporting works fine until error message is displayed below the "show log" text area stating "Reporting disabled because the backtrace is unusable"
Report should work fine. If not it should tell me why.
If you need a copy of some of my problem directories please provide a PGP key ID (with an email address). I'll not upload all of them here.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
I believe the issue was caused by the transition from yum to dnf.