Bug 521661 – crash in Evolution: Trying to open a message...

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 521661 - crash in Evolution: Trying to open a message...


Summary:	crash in Evolution: Trying to open a message...


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-10 20:13 UTC by eduardo.hoesker
Modified:	2008-03-20 14:09 UTC

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

Description eduardo.hoesker 2008-03-10 20:13:39 UTC

What were you doing when the application crashed?
Trying to open a message received


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

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mac4Lin_GTK_v0.4
Icon Theme: Mac4Lin_Icons_v0.4

Memory status: size: 66191360 vsize: 66191360 resident: 10752000 share: 8417280 rss: 10752000 rss_rlim: 4294967295
CPU usage: start_time: 1205175354 rtime: 76 utime: 60 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65ad6d0 (LWP 3372)]
[New Thread 0xb63d3b90 (LWP 3378)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 192014

Thread 1 (Thread 0xb65ad6d0 (LWP 3372))

#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 ??
from /usr/lib/libexchange-storage-1.2.so.3
#16 ??
#17 ??
from /usr/lib/libexchange-storage-1.2.so.3
#18 ??
#19 ??
#20 ??
#0 __kernel_vsyscall



----------- .xsession-errors (26 sec old) ---------------------
(evolution:3316): e-spinner.c-WARNING **: Cannot extract frame (108, 0) from the grid
(evolution:3316): e-spinner.c-WARNING **: Cannot extract frame (144, 0) from the grid
(evolution:3316): e-spinner.c-WARNING **: Cannot extract frame (180, 0) from the grid
(evolution:3316): e-spinner.c-WARNING **: Cannot extract frame (216, 0) from the grid
(evolution:3316): e-spinner.c-WARNING **: Cannot extract frame (252, 0) from the grid
--------------------------------------------------

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