Bug 751513 - [abrt] evolution-2.32.3-1.fc14: g_object_ref: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.3-1.fc14: g_object_ref: Process /usr/bin/evolution was ...
Keywords:
Status: CLOSED DUPLICATE of bug 668537
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8f6168bcb67568fd3f1f9e60f06...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-05 01:22 UTC by Jim Gribbin
Modified: 2011-11-07 07:28 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-11-07 07:28:46 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (39.52 KB, text/plain)
2011-11-05 01:22 UTC, Jim Gribbin 		no flags Details
View All

Description Jim Gribbin 2011-11-05 01:22:40 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 40464 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 229212160 bytes
crash_function: g_object_ref
executable: /usr/bin/evolution
kernel: 2.6.35.14-100.fc14.i686
package: evolution-2.32.3-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1320455650
uid: 500

How to reproduce
-----
1. 
2.
3.
I don't know how to reproduce. I was moving contacts from 1 address book to another and about 2/3 the way through, Evolution crashed.

I had selected several to be moved and was moving them at one time.

I am uncertain as to how many, maybe 3 dozen.
Comment 1 Jim Gribbin 2011-11-05 01:22:43 UTC 
Created attachment 531868 [details]
File: backtrace
Comment 2 Milan Crha 2011-11-07 07:28:46 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. Note this is fixed in 3.0.0 of evolution.

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