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 330299 - Evolution crashes when sending mail via Exchange server
Evolution crashes when sending mail via Exchange server
Status: RESOLVED DUPLICATE of bug 327827
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.4.x
Other Linux
: High critical
: 2.5
Assigned To: Sankar P
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-02-07 18:57 UTC by matt.yun
Modified: 2006-03-16 06:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description matt.yun 2006-02-07 18:57:06 UTC
From: ma <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.12.1
Subject: Evolution crashes when sending mail via Exchange server

Distribution: Ubuntu 5.10 (breezy)
Package: Evolution
Severity: Normal
Version: GNOME2.12.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Evolution crashes when sending mail via Exchange server
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
Evolution crashes when sending mail via remote Exchange server

Steps to reproduce the crash:
1.  Compose new message or reply to a message
2. Click 'Send' button
3.

Expected Results:
Error dialog pops up with message 'The Application "evolution" has quit
unexpectedly.'

Then when closing Evolution, message pops up 'Warning The window
"Evolution - Mail" is not responding'


How often does this happen?
Every single time since around January 31, 2006.

Additional Information:
Using Ubuntu 5.10.  There were no problems with Evolution and my
employer's remote Exchange server since I installed Ubuntu 5.10 until
the January 31, 2006.  I do not know whether there have been recent
changes to the Exchange server (the server is located in Ottawa, and I'm
in Vancouver).


Debugging Information:

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230623936 (LWP 9520)]
[New Thread -1322767440 (LWP 12168)]
[New Thread -1307272272 (LWP 9581)]
[New Thread -1308623952 (LWP 9580)]
[New Thread -1298879568 (LWP 9571)]
[New Thread -1290355792 (LWP 9570)]
[New Thread -1281168464 (LWP 9560)]
[New Thread -1272775760 (LWP 9559)]
[New Thread -1264383056 (LWP 9534)]
[New Thread -1255908432 (LWP 9533)]
[New Thread -1247515728 (LWP 9532)]
[New Thread -1238467664 (LWP 9531)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 9 (Thread -1264383056 (LWP 9534))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 _L_mutex_lock_33
    from /lib/tls/i686/cmov/libpthread.so.0
  • #3 ??
  • #4 ??
  • #5 ??
    from /lib/tls/i686/cmov/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #13 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #14 es_menu_hook_get_type
  • #15 <signal handler called>
  • #16 camel_object_cast
    from /usr/lib/libcamel-1.2.so.0
  • #17 mail_fetch_mail
    from /usr/lib/evolution/2.4/components/libevolution-mail.so
  • #18 mail_fetch_mail
    from /usr/lib/evolution/2.4/components/libevolution-mail.so
  • #19 mail_cancel_all
    from /usr/lib/evolution/2.4/components/libevolution-mail.so
  • #20 e_thread_busy
    from /usr/lib/libedataserver-1.2.so.4
  • #21 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #22 clone
    from /lib/tls/i686/cmov/libc.so.6



--

Matthew Yun
Vancouver, B.C. Canada
matt.yun@gmail.com

Browsing with Mozilla Firefox
www.mozilla.org




------- Bug created by bug-buddy at 2006-02-07 18:57 -------

Comment 1 parthasarathi susarla 2006-02-08 07:28:19 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 matt.yun 2006-02-13 22:39:29 UTC
Sorry for the delay in my response, but I had to learn how get a stack trace with debugging symbols; thanks for the link, by the way.  I used the gdb-only method.  Here are the results:

***

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1272751184 (LWP 9698)]
0xb7d7a539 in camel_object_cast () from /usr/lib/libcamel-1.2.so.0
(gdb) thread apply all bt

Thread 6 (Thread -1272751184 (LWP 9698))

  • #0 camel_object_cast
    from /usr/lib/libcamel-1.2.so.0
  • #1 mail_fetch_mail
    from /usr/lib/evolution/2.4/components/libevolution-mail.so
  • #2 mail_fetch_mail
    from /usr/lib/evolution/2.4/components/libevolution-mail.so
  • #3 mail_cancel_all
    from /usr/lib/evolution/2.4/components/libevolution-mail.so
  • #4 e_thread_busy
    from /usr/lib/libedataserver-1.2.so.4
  • #5 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #6 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 3 parthasarathi susarla 2006-02-16 10:40:22 UTC
Thanks for the stack trace. Reassigning the component to connector
Comment 4 Sankar P 2006-02-28 09:51:03 UTC
Stacktraces very similar to 327827.
May not be specific to exchange.

*** This bug has been marked as a duplicate of 327827 ***
Comment 5 matt.yun 2006-03-16 06:34:36 UTC
Sending mail now works again.  I did not do anything specific to my system, except  apt-get upgrade.