Bug 651025 - [abrt] evolution-2.32.0-2.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.0-2.fc14: Process /usr/bin/evolution was killed by sign...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:be9c4d6e1fda0a97a90e35e7f5e...
: 656965 672781 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-08 17:07 UTC by Didi Hoffmann
Modified: 2011-01-26 16:35 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 07:06:53 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (52.95 KB, text/plain)
2010-11-08 17:07 UTC, Didi Hoffmann 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 634387 0 None None None Never

Description Didi Hoffmann 2010-11-08 17:07:22 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: bbdb_sync_buddy_list_in_thread
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Tried to sync with pidgin
time: 1289235202
uid: 500
Comment 1 Didi Hoffmann 2010-11-08 17:07:24 UTC 
Created attachment 458817 [details]
File: backtrace
Comment 2 Milan Crha 2010-11-09 07:06:53 UTC 
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=634387
Comment 3 Milan Crha 2010-11-25 10:10:28 UTC 
*** Bug 656965 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2011-01-26 16:35:01 UTC 
*** Bug 672781 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.