Bug 534026 – crash in Evolution Mail and Calendar: Writing a new message, f...

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 534026 - crash in Evolution Mail and Calendar: Writing a new message, f...


Summary:	crash in Evolution Mail and Calendar: Writing a new message, f...


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-05-20 11:55 UTC by uwe
Modified:	2008-05-21 04:08 UTC

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

Description uwe 2008-05-20 11:55:09 UTC

What were you doing when the application crashed?
Writing a new message, filling in CC field


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.1 2008-04-30 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-14.fc9.i686 #1 SMP Thu May 1 06:28:41 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 61820928 vsize: 61820928 resident: 13271040 share: 10231808 rss: 13271040 rss_rlim: 4294967295
CPU usage: start_time: 1211276369 rtime: 526 utime: 431 stime: 95 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 0xb7fd1730 (LWP 13312)]
[New Thread 0xb7ccfb90 (LWP 13314)]
0x00110416 in __kernel_vsyscall ()

+ Trace 198212

Thread 1 (Thread 0xb7fd1730 (LWP 13312))

#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 manager_populate
at e-book-backend-gal.c line 1235
#22 build_contact_from_entry
at e-book-backend-gal.c line 1430
#23 ldap_search_handler
at e-book-backend-gal.c line 1626
#24 poll_ldap
at e-book-backend-gal.c line 1578
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_loop_run
from /lib/libglib-2.0.so.0
#29 bonobo_main
from /usr/lib/libbonobo-2.so.0
#30 main
at main.c line 238
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
  
  
  
  
  
  
  
report junk?? CONTACT FEDEX EXPRESS COMPANY BENIN
BBDB spinning up...
bbdb: Buddy list has changed since last sync.
bbdb: Buddy list has changed since last sync.
(evolution:13304): libebook-WARNING **: EBookView: Exception while releasing BookView
--------------------------------------------------

Comment 1 Akhil Laddha 2008-05-21 04:08:47 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 ***