Bug 692865 - [abrt] evolution-data-server-2.32.2-1.fc14: call_dtor: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.2-1.fc14: call_dtor: Process /usr/libexec/e...
Keywords:
Status: CLOSED DUPLICATE of bug 660012
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b277e8c6057dc59613fead22891...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-01 12:56 UTC by Jobst Hoffmann
Modified: 2011-04-04 10:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-04 10:06:15 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (21.38 KB, text/plain)
2011-04-01 12:56 UTC, Jobst Hoffmann 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jobst Hoffmann 2011-04-01 12:56:16 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 21888 bytes
cmdline: /usr/libexec/e-addressbook-factory
comment: Perform the three steps mentioned above
component: evolution-data-server
Attached file: coredump, 84475904 bytes
crash_function: call_dtor
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301662285
uid: 10637

How to reproduce
-----
1. Just start the computer
2. after a while
3. evolution crashes
Comment 1 Jobst Hoffmann 2011-04-01 12:56:20 UTC 
Created attachment 489383 [details]
File: backtrace
Comment 2 Milan Crha 2011-04-04 10:06:15 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

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