evolution crashed with SIGSEGV

[Hatem MASMOUDI]

Evolution crash when adding a new account.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution 3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Wed Aug 15 06:05:25 2012
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120814.1)
ProcCmdline: evolution
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc4e13ab610: mov 0x8(%rax),%rdi
 PC (0x7fc4e13ab610) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libcamel-1.2.so.39
 ?? () from /usr/lib/libcamel-1.2.so.39
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: evolution crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 imapx_query_auth_types_sync (service=<optimized out>, cancellable=<optimized out>, error=<optimized out>) at camel-imapx-store.c:290
 service_query_auth_types_thread (simple=0x7fc4e7a8bb20, object=0x7fc4e7857660, cancellable=0x7fc4e7a491e0) at camel-service.c:944
 run_in_thread (job=<optimized out>, c=0x7fc4e7a491e0, _data=0x7fc4e7a64d70) at /build/buildd/glib2.0-2.33.8/./gio/gsimpleasyncresult.c:869
 io_job_thread (data=0x7fc4e7c5b770, user_data=<optimized out>) at /build/buildd/glib2.0-2.33.8/./gio/gioscheduler.c:162
 g_thread_pool_thread_proxy (data=<optimized out>) at /build/buildd/glib2.0-2.33.8/./glib/gthreadpool.c:309

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.