Bug 540863 – crash in Evolution Mail and Calendar: Reading mail

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 540863 - crash in Evolution Mail and Calendar: Reading mail


Summary:	crash in Evolution Mail and Calendar: Reading mail


Status:	RESOLVED DUPLICATE of bug 512605

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.22.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-30 06:42 UTC by uwe
Modified:	2008-06-30 07:51 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description uwe 2008-06-30 06:42:42 UTC

What were you doing when the application crashed?
Reading mail


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.2 2008-05-28 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.6-55.fc9.i686 #1 SMP Tue Jun 10 16:27:49 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 142143488 vsize: 142143488 resident: 73424896 share: 10989568 rss: 73424896 rss_rlim: 4294967295
CPU usage: start_time: 1214807092 rtime: 274 utime: 226 stime: 48 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

[Thread debugging using libthread_db enabled]
[New Thread 0xb7fd3730 (LWP 3871)]
[New Thread 0xb7cd1b90 (LWP 3873)]
0x00110416 in __kernel_vsyscall ()

+ Trace 201724

Thread 1 (Thread 0xb7fd3730 (LWP 3871))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 __kernel_vsyscall
#10 raise
from /lib/libc.so.6
#11 abort
from /lib/libc.so.6
#12 __assert_fail
from /lib/libc.so.6
#13 ber_flush2
from /usr/lib/libexchange-storage-1.2.so.3
#14 ldap_int_flush_request
from /usr/lib/libexchange-storage-1.2.so.3
#15 ldap_send_server_request
from /usr/lib/libexchange-storage-1.2.so.3
#16 ldap_send_initial_request
from /usr/lib/libexchange-storage-1.2.so.3
#17 ldap_ntlm_bind
from /usr/lib/libexchange-storage-1.2.so.3
#18 connect_ldap
at e2k-global-catalog.c line 243
#19 gc_search
at e2k-global-catalog.c line 396
#20 e2k_global_catalog_lookup
at e2k-global-catalog.c line 798
#21 get_message
at mail-stub-exchange.c line 2344
#22 connection_handler
at mail-stub.c line 271
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 bonobo_main
from /usr/lib/libbonobo-2.so.0
#28 main
at main.c line 238



----------- .xsession-errors (119 sec old) ---------------------
feed Official Google Maps API Blog
BBDB spinning up...
bbdb: Buddy list has changed since last sync.
(evolution:3906): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GThemedIcon' has no property named `names'
(evolution:3906): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed
(evolution:3906): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed
bbdb: Synchronizing buddy list to contacts...
bbdb: Done syncing buddy list to contacts.
component_id:OAFIID:GNOME_Evolution_RSS:2.22
rf->0x90da780
(evolution:3906): GLib-GObject-WARNING **: gsignal.c:1669: signal `value-changed' is invalid for instance `0x9f11398'
--------------------------------------------------

Comment 1 Akhil Laddha 2008-06-30 07:51:35 UTC

Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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