Bug 529948 – crash in Evolution: I was moving from one ne...

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 529948 - crash in Evolution: I was moving from one ne...


Summary:	crash in Evolution: I was moving from one ne...


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-04-25 19:17 UTC by pellicci
Modified:	2008-04-27 01:01 UTC

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

Description pellicci 2008-04-25 19:17:00 UTC

What were you doing when the application crashed?
I was moving from one new email to the next new one


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Mac4Lin_Icons_v0.4

Memory status: size: 65953792 vsize: 65953792 resident: 13062144 share: 10207232 rss: 13062144 rss_rlim: 4294967295
CPU usage: start_time: 1209146394 rtime: 50 utime: 46 stime: 4 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 0xb66af740 (LWP 3626)]
[New Thread 0xb63d8b90 (LWP 3628)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 196128

Thread 1 (Thread 0xb66af740 (LWP 3626))

#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 ---------------------
(evolution:3612): e-spinner.c-WARNING **: Cannot extract frame (108, 0) from the grid
(evolution:3612): e-spinner.c-WARNING **: Cannot extract frame (144, 0) from the grid
(evolution:3612): e-spinner.c-WARNING **: Cannot extract frame (180, 0) from the grid
(evolution:3612): e-spinner.c-WARNING **: Cannot extract frame (216, 0) from the grid
(evolution:3612): e-spinner.c-WARNING **: Cannot extract frame (252, 0) from the grid
--------------------------------------------------

Comment 1 André Klapper 2008-04-27 01:01:02 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 ***