After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 623834 - evolution crashed with SIGSEGV in camel_exchange_utils_send_message()
evolution crashed with SIGSEGV in camel_exchange_utils_send_message()
Status: RESOLVED DUPLICATE of bug 612178
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.30.x
Other Linux
: Normal critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2010-07-08 13:09 UTC by Pedro Villavicencio
Modified: 2010-07-08 23:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description Pedro Villavicencio 2010-07-08 13:09:11 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/602907

"Consistently happen when trying to send email resting in the Outbox."

".

+ Trace 222749

Thread 5 (process 16569)

  • #0 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 111
  • #1 ??
    from /usr/lib/libsoup-2.4.so.1
  • #2 pthread_create
    from /lib/libpthread.so.0
  • #3 ??
  • #4 ??
    from /lib/libglib-2.0.so.0
  • #5 ??

Thread 1 (process 16567)

  • #0 camel_exchange_utils_send_message
    at camel-exchange-utils.c line 3005
  • #1 exchange_send_to
    at camel-exchange-transport.c line 167
  • #2 camel_transport_send_to
    at camel-transport.c line 133
  • #3 send_queue_exec
    at mail-ops.c line 545
  • #4 mail_msg_proxy
    at mail-mt.c line 471
  • #5 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.25.10/glib/gthreadpool.c line 315
  • #6 g_thread_create_proxy
    at /build/buildd/glib2.0-2.25.10/glib/gthread.c line 1898
  • #7 start_thread
    from /lib/libpthread.so.0
  • #8 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130 
Current language:  auto; currently c"
Comment 1 Fabio Durán Verdugo 2010-07-08 23:22:40 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 612178 ***