Bug 600882 - [abrt] crash in gramps-3.2.2-1.fc13: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gramps-3.2.2-1.fc13: raise: Process /usr/bin/python was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 599581
Alias: None
Product: Fedora
Classification: Fedora
Component: gramps
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeffrey C. Ollie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:60c23caec2ee34c0eefddbf2823...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-06 14:00 UTC by Raymond Vassieux
Modified: 2010-11-08 17:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 17:43:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (36.50 KB, text/plain)
2010-06-06 14:00 UTC, Raymond Vassieux 		no flags Details
View All

Description Raymond Vassieux 2010-06-06 14:00:10 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python -O /usr/share/gramps/gramps.py
component: gramps
crash_function: raise
executable: /usr/bin/python
global_uuid: 60c23caec2ee34c0eefddbf282313525e383cc2c
kernel: 2.6.33.5-112.fc13.i686.PAE
package: gramps-3.2.2-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
I made an export of the XML database on USB key. At the end of the export Gramps turn off alone and I had this bug annoncement.
The file on USB key is in good condition and can be read on an another computer.
Comment 1 Raymond Vassieux 2010-06-06 14:00:12 UTC 
Created attachment 421598 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 17:43:07 UTC 

*** This bug has been marked as a duplicate of bug 599581 ***
Comment 3 Karel Klíč 2010-11-08 17:43:07 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #599581.

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