Bug 674214 - [abrt] evolution-2.32.1-1.fc14: group_changed_callback: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: group_changed_callback: Process /usr/bin/evol...
Keywords:
Status: CLOSED UPSTREAM
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:23744dd419cb60427f0f6244074...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 01:06 UTC by Bojan Smojver
Modified: 2011-02-01 15:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-01 15:18:39 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (34.60 KB, text/plain)
2011-02-01 01:06 UTC, Bojan Smojver 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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

Description Bojan Smojver 2011-02-01 01:06:02 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: group_changed_callback
executable: /usr/bin/evolution
kernel: 2.6.35.10-74.fc14.i686
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: 1296521849
uid: 15162

How to reproduce
-----
1. Attempted to add a new contact (exchange).
2. Got prompted for password.
3. Crash.
Comment 1 Bojan Smojver 2011-02-01 01:06:05 UTC 
Created attachment 476295 [details]
File: backtrace
Comment 2 Milan Crha 2011-02-01 15:18:39 UTC 
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=641155
Note You need to log in before you can comment on or make changes to this bug.