Bug 1100329 - gnome-abrt-0.3.6-1.fc20: python2.7 killed by SIGABRT
Summary: gnome-abrt-0.3.6-1.fc20: python2.7 killed by SIGABRT
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 20
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-22 14:37 UTC by Randy Barlow
Modified: 2016-12-01 00:47 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-09 14:13:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
core_backtrace (33.30 KB, text/plain)
2014-05-22 14:37 UTC, Randy Barlow
no flags Details

Description Randy Barlow 2014-05-22 14:37:43 UTC
Created attachment 898402 [details]
core_backtrace

For a few weeks I've been unable to use abrt to report crashes, as abrt crashes itself. Humorously, it does show its own crash as a thing I can report, but it also crashes when I try to report that.

I'm not sure which information would be helpful to add to this report, but this is easily reproducible on my machine and I'd be happy to provide information to help if others cannot reproduce.

I've attached the core_backtrace file.

Comment 1 Jakub Filak 2014-06-09 12:46:43 UTC
Thank you for taking the time to report this crash. "core_backtrace" file shows me that the problem is rather in pango or gtk3.

The full backtrace would be useful. Please, go to the problem directory and run:

$ abrt-action-analyze-ccpp-local

The command should create "backtrace" file.


FYI: ABRT has also command-line interface.

$ yum install abrt-cli
$ abrt-cli list
$ abrt-cli report $PROBLEMID

Comment 2 Randy Barlow 2014-06-09 14:13:57 UTC
Hi Jakub, thank you for the comment. [Un]fortunately, ABRT is now working perfectly on my system, so I can no longer reproduce this error. Presumably, an update to pango or gtk3 may have resolved the problem for me. I don't seem to have any of the problem directories around on my system anymore either.

Your note is still helpful in case this happens again.

I will humorously close my own bug as WORKSFORME.


Note You need to log in before you can comment on or make changes to this bug.