Bug 650190 - [abrt] evolution-2.32.0-2.fc14: action_contact_new_cb: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.0-2.fc14: action_contact_new_cb: Process /usr/bin/evolu...
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:e1a3d97aaadb0252748653f4fea...
: 654178 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-05 14:02 UTC by jbox_ny
Modified: 2010-11-18 10:03 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-05 14:59:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (45.48 KB, text/plain)
2010-11-05 14:02 UTC, jbox_ny 		no flags Details
View All


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

Description jbox_ny 2010-11-05 14:02:33 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution calendar:///?startdate=20101112T050000Z
component: evolution
crash_function: action_contact_new_cb
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)
time: 1288965558
uid: 500

How to reproduce
-----
1. I was entering my schedule on evolution
2. I clicked on add contact for the very first time and it crashed
3.
Comment 1 jbox_ny 2010-11-05 14:02:36 UTC 
Created attachment 458092 [details]
File: backtrace
Comment 2 Milan Crha 2010-11-05 14:59:49 UTC 
Thanks for a bug report. I moved this upstream, please see [1] for any further updates.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=634088
Comment 3 Milan Crha 2010-11-18 10:03:07 UTC 
*** Bug 654178 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.