Bug 1047593
| Summary: | A problem with ABRT | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | D. Charles Pyle <dcharlespyle> | ||||
| Component: | gnome-abrt | Assignee: | Jakub Filak <jfilak> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | dcharlespyle, jberan, jfilak | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:258ec248b868801ad69a65e37427a45fdb587718 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-06-10 08:44:50 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Thank you for the report. Could you please attach the entire crash folder? Created attachment 844504 [details]
Compressed directory of one abrt error report
Here is one of the directories in the abrt directory. Let me know if you need more. A lot of them won't copy out without generating errors, though. Caja isn't being very stable at the moment.
It looks like that your 'coredump' file is corrupted. 'backtrace' file contains the following warning: ... warning: Corrupted shared library list: 0x3d39621700 != 0x0 Failed to read a valid object file image from memory. ... I get the same message when I try to generate the backtrace from your coredump localy. However, it seems that the root cause is not in mate-volume-control itself because if I 'kill' mate-volume-control process by SIGSEGV, abrt detectets the crash and the retrace server generates a good backtrace for that crash. If you have time, please run the following commands and report the results here: $ mate-volume-control & $ kill -SEGV %% $ <find the crash directory> $ cd $CRASH_DIRECTORY $ report-cli -e analyze_RetraceServer -- ./ $ cat backtrace $ cat backtrace_rating I recently had to reinstall my entire system due to some filesystem corruption while using btrfs. I no longer am having problems. |
Description of problem: Ever since updating abrt, most of my reports fail to be submitted because the backtrace is unusable. This week, every report has failed. The last was as follows: -- 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). 'YES' Querying server settings Preparing an archive to upload Uploading 1087576 bytes Upload successful Retrace job started Preparing environment for backtrace generation ............................................... Cleaning environment after backtrace generation Retrace job finished successfully Looking for similar problems in bugzilla This is followed by the error: "Reporting disabled because the backtrace is unusable." Version-Release number of selected component: gnome-abrt-0.3.4 Additional info: reporter: libreport-2.1.10 kernel: 3.12.6-300.fc20.x86_64 type: libreport