Bug 639956

Summary: [abrt] childsplay-1.5.1-1.fc13: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Elias Oliveira de Jesus <flama.es>
Component: childsplayAssignee: Hans de Goede <hdegoede>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: fedora, p
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:744564055dd483a418c8db93b0f2e497094220e7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-01 12:58:47 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:
Description Flags
File: backtrace none

Description Elias Oliveira de Jesus 2010-10-04 12:13:28 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/childsplay
component: childsplay
crash_function: raise
executable: /usr/bin/python
kernel: 2.6.34.7-56.fc13.x86_64
package: childsplay-1.5.1-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1286029735
uid: 500
Comment 1 Elias Oliveira de Jesus 2010-10-04 12:13:33 UTC 
Created attachment 451387 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2010-12-30 19:00:24 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Hans de Goede 2011-01-01 12:58:47 UTC 
Hi,

This is the new childsplay maintainer. It seems that childsplay aborted due to
a python error. But abrt did not include the python error in the logs.

If you see this error again, please see if there are any messages on the terminal from which you started childsplay, or if you started it from a menu entry, in ~/.xsession-errors. Then file a new bug including the Python messages in the description of the bug.

Thanks & Regards,

Hans