Bug 684588 - [abrt] sugar-0.92.0-2.fc15: PyArg_ParseTupleAndKeywords: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] sugar-0.92.0-2.fc15: PyArg_ParseTupleAndKeywords: Process /usr/bin/pyt...
Keywords:
Status: CLOSED DUPLICATE of bug 701209
Alias: None
Product: Fedora
Classification: Fedora
Component: sugar
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simon Schampijer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:18231a9808db2d205f1ed422d1d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-13 16:37 UTC by satellitgo
Modified: 2012-03-21 14:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 14:41:17 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (51.61 KB, text/plain)
2011-03-13 16:37 UTC, satellitgo 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description satellitgo 2011-03-13 16:37:55 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 52847 bytes
cmdline: python /usr/bin/sugar-activity webactivity.WebActivity -s -b org.laptop.Surf -a e82dd6f9ceeb650cdb89f2f0f3932caf4733e5b3
component: sugar
Attached file: coredump, 1138167808 bytes
crash_function: PyArg_ParseTupleAndKeywords
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 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1300023470
uid: 500

How to reproduce
-----
1.run sugar
2.try to load surf-115 .xo activity
3.
Comment 1 satellitgo 2011-03-13 16:37:57 UTC 
Created attachment 484017 [details]
File: backtrace
Comment 2 satellitgo 2011-03-20 23:56:33 UTC 
Package: sugar-0.92.0-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1.start sugar-desktop
2.try to start sugar-surf-115.xo application
3.exit sugar
Comment 3 abrt-bot 2012-03-21 14:41:17 UTC 
Backtrace analysis found this bug to be similar to bug #701209, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 701209 ***
Note You need to log in before you can comment on or make changes to this bug.