Bug 684503

Summary: [abrt] sugar-0.92.0-2.fc15: handle_error: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: satellitgo
Component: sugarAssignee: Simon Schampijer <simon>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: bernie+fedora, johnp, pbrobinson, satellitgo, sebastian, simon, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:40591f6dec052b37cd47724107da799db594a4b1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:20:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description satellitgo 2011-03-13 05:21:52 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 68974 bytes
cmdline: python /usr/bin/sugar-activity activity.MazeActivity -b vu.lux.olpc.Maze -a df5e1568a4d10060c9d7efeb73ca88b3950a48bc
component: sugar
Attached file: coredump, 66719744 bytes
crash_function: handle_error
executable: /usr/bin/python
kernel: 2.6.38-0.rc8.git0.1.fc15.x86_64
package: sugar-0.92.0-2.fc15
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1299989188
uid: 500

How to reproduce
-----
1.start sugar-desktop
2.sugar-emulator
3.
Comment 1 satellitgo 2011-03-13 05:21:54 UTC 
Created attachment 483949 [details]
File: backtrace
Comment 2 satellitgo 2011-03-13 05:27:56 UTC 
3.start sugar-maze in sugar
Comment 3 abrt-bot 2012-03-20 16:20:19 UTC 
Backtrace analysis found this bug to be similar to bug #739951, closing as duplicate.

Bugs which were found to be similar to this bug: bug #656099, bug #656164, bug #739951

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 739951 ***