Bug 528233 – crash in Evolution Mail and Calendar: ldap lookup caused crash

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 528233 - crash in Evolution Mail and Calendar: ldap lookup caused crash


Summary:	crash in Evolution Mail and Calendar: ldap lookup caused crash


Status:	RESOLVED DUPLICATE of bug 303067

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-04-15 15:28 UTC by Wendell MacKenzie
Modified:	2008-04-15 19:15 UTC

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

Description Wendell MacKenzie 2008-04-15 15:28:39 UTC

What were you doing when the application crashed?
ldap lookup caused crash


Distribution: openSUSE 10.3 (i586)
Gnome Release: 2.20.0 2007-09-22 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.22.17-0.1-bigsmp #1 SMP 2008/02/10 20:01:04 UTC i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Chlorophyll
Icon Theme: Industrial

Memory status: size: 76038144 vsize: 76038144 resident: 15884288 share: 10625024 rss: 26509312 rss_rlim: 3609548800
CPU usage: start_time: 1208265245 rtime: 150 utime: 132 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb62cd6c0 (LWP 4745)]
[New Thread 0xb54ffb90 (LWP 27653)]
[New Thread 0xb5e82b90 (LWP 27652)]
[New Thread 0xb5ec3b90 (LWP 4748)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 195293

Thread 3 (Thread 0xb5e82b90 (LWP 27652))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 run_bug_buddy
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 check_if_gdb
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 ldap_search_ext
from /usr/lib/libldap-2.3.so.0
#14 start_book_view
at e-book-backend-gal.c line 1821
#15 e_book_backend_start_book_view
at e-book-backend.c line 305
#16 impl_GNOME_Evolution_Addressbook_BookView_start
at e-data-book-view.c line 492
#17 _ORBIT_skel_small_GNOME_Evolution_Addressbook_BookView_start
at Evolution-DataServer-Addressbook-common.c line 36
#18 ??
from /usr/lib/libORBit-2.so.0
#19 ??
#20 ??



----------- .xsession-errors (7678 sec old) ---------------------
(evolution:4724): camel-WARNING **: DEBUG: interrupted select...sleeping 100 millisecs
(evolution:4724): camel-WARNING **: DEBUG: interrupted select...sleeping 100 millisecs
(evolution:4724): camel-WARNING **: DEBUG: back from usleep...
(evolution:4724): camel-WARNING **: DEBUG: back from usleep...
(evolution:4724): camel-WARNING **: DEBUG: interrupted select...sleeping 100 millisecs
(evolution:4724): camel-WARNING **: DEBUG: back from usleep...
(evolution:4724): camel-WARNING **: DEBUG: interrupted select...sleeping 100 millisecs
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2008-04-15 19:15:19 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 303067 ***