Bug 660103 - [abrt] evolution-2.32.1-1.fc14: (SIGSEGV) propfind_msg, e2k_context_propfind, unmangle_sender_field
Summary: [abrt] evolution-2.32.1-1.fc14: (SIGSEGV) propfind_msg, e2k_context_propfind,...
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:2376a83a84decc0d381e9f0b4c3...
: 696188 701155 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-05 14:53 UTC by Matthew Saltzman
Modified: 2011-05-02 06:06 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-06 07:55:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (46.43 KB, text/plain)
2010-12-05 14:53 UTC, Matthew Saltzman 		no flags Details
View All

Description Matthew Saltzman 2010-12-05 14:53:10 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Crash occurred while sycing OWA Exchange account on startup.  After a couple startups, Evo runs stably for a while.
component: evolution
crash_function: propfind_msg
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291560532
uid: 500

How to reproduce
-----
1. Start evolution (with OWA Exchange account)
2.
3.
Comment 1 Matthew Saltzman 2010-12-05 14:53:14 UTC 
Created attachment 464853 [details]
File: backtrace
Comment 2 Milan Crha 2010-12-06 07:55:43 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=636565
Comment 3 Milan Crha 2011-04-14 05:17:08 UTC 
*** Bug 696188 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2011-05-02 06:06:05 UTC 
*** Bug 701155 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.