Bug 518322 – crash in Evolution Mail: Attempting to connect to...

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 518322 - crash in Evolution Mail: Attempting to connect to...


Summary:	crash in Evolution Mail: Attempting to connect to...


Status:	RESOLVED DUPLICATE of bug 451816

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.12.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-23 22:51 UTC by jtl2011
Modified:	2008-02-24 13:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description jtl2011 2008-02-23 22:51:10 UTC

What were you doing when the application crashed?
Attempting to connect to my email (Microsoft Exchange)


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-1-powerpc #1 Mon Feb 11 12:53:42 CET 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 159690752 vsize: 159690752 resident: 44728320 share: 27439104 rss: 44728320 rss_rlim: 4294967295
CPU usage: start_time: 1203806287 rtime: 1973 utime: 1887 stime: 86 cutime:3 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x480488b0 (LWP 23966)]
[New Thread 0x4c5894b0 (LWP 24065)]
[New Thread 0x4bd894b0 (LWP 24062)]
[New Thread 0x49d894b0 (LWP 24061)]
[New Thread 0x491a54b0 (LWP 24033)]
[New Thread 0x4b5894b0 (LWP 24030)]
[New Thread 0x4ad894b0 (LWP 24029)]
[New Thread 0x4a5894b0 (LWP 24028)]
[New Thread 0x489a54b0 (LWP 24009)]
(no debugging symbols found)
0x0f9752a4 in waitpid () from /lib/libpthread.so.0

+ Trace 190236

Thread 1 (Thread 0x480488b0 (LWP 23966))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
#5 <signal handler called>
#6 e_account_set_string
from /usr/lib/libedataserver-1.2.so.9
#7 exchange_config_listener_authenticate
from /usr/lib/evolution/2.12/plugins/liborg-gnome-exchange-operations.so
#8 exchange_operations_get_exchange_account
from /usr/lib/evolution/2.12/plugins/liborg-gnome-exchange-operations.so
#9 org_gnome_exchange_commit
from /usr/lib/evolution/2.12/plugins/liborg-gnome-exchange-operations.so
#10 ??
from /usr/lib/evolution/2.12/libeutil.so.0
#11 e_plugin_invoke
from /usr/lib/evolution/2.12/libeutil.so.0
#12 ??
from /usr/lib/evolution/2.12/libeutil.so.0
#13 e_config_commit
from /usr/lib/evolution/2.12/libeutil.so.0
#14 ??
from /usr/lib/evolution/2.12/libeutil.so.0
#15 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#31 ??
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#34 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgobject-2.0.so.0
#38 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#39 ??
from /usr/lib/libgobject-2.0.so.0
#40 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#41 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgdk-x11-2.0.so.0
#46 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#47 ??
from /usr/lib/libglib-2.0.so.0
#48 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#49 bonobo_main
from /usr/lib/libbonobo-2.so.0
#50 ??
#51 ??
from /lib/libc.so.6
#52 __libc_start_main
from /lib/libc.so.6
#53 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
Find Items 9
Couldn't Get password 9
get jtl2011 exchange://jtl2011;auth=Basic@mail.rit.edumymail.rit.edu/
Find Items 9
Couldn't Get password 9
Remember exchange://jtl2011@mymail.rit.edu/: 0/1
get jtl2011 exchange://jtl2011;auth=Basic@mymail.rit.edumymail.rit.edu/
Find Items 9
Couldn't Get password 9
Remember exchange://jtl2011;auth=Basic@mymail.rit.edumymail.rit.edu/: 0/2
Remember exchange://jtl2011@mymail.rit.edu/: 0/1
get jtl2011 exchange://jtl2011;auth=NTLM@mail.rit.edu/
Find Items 9
Couldn't Get password 9
Remember exchange://jtl2011;auth=NTLM@mail.rit.edu/: 0/3
--------------------------------------------------

Comment 1 Susana 2008-02-24 13:06:17 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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