Bug 523036 – crash in Evolution:

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 523036 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 512605

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.12.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-03-17 20:01 UTC by jmartens
Modified:	2008-03-20 14:09 UTC

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

Description jmartens 2008-03-17 20:01:28 UTC

What were you doing when the application crashed?



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

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 56463360 vsize: 56463360 resident: 27668480 share: 9359360 rss: 27668480 rss_rlim: 4294967295
CPU usage: start_time: 1205778341 rtime: 103 utime: 95 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb669f8e0 (LWP 26861)]
[New Thread 0xb640ab90 (LWP 26863)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 192720

Thread 1 (Thread 0xb669f8e0 (LWP 26861))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/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 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 __assert_fail
from /lib/i686/cmov/libc.so.6
#10 ber_flush2
from /usr/lib/liblber-2.4.so.2
#11 ldap_int_flush_request
from /usr/lib/libldap_r-2.4.so.2
#12 ldap_send_server_request
from /usr/lib/libldap_r-2.4.so.2
#13 ldap_send_initial_request
from /usr/lib/libldap_r-2.4.so.2
#14 ldap_ntlm_bind
from /usr/lib/libldap_r-2.4.so.2
#15 connect_ldap
at e2k-global-catalog.c line 243
#16 gc_search
#17 e2k_global_catalog_lookup
at e2k-global-catalog.c line 796
#18 get_message
at mail-stub-exchange.c line 2266
#19 connection_handler
at mail-stub.c line 271
#20 ??
from /usr/lib/libglib-2.0.so.0
#21 ??
#22 ??
#23 ??
#24 ??
from /usr/lib/libglib-2.0.so.0
#25 ??
#26 ??
#27 ??
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (127 sec old) ---------------------
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo contex
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-03-20 14:09:03 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 ***