Bug 479996 – crash in Evolution Mail: crash on exit

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 479996 - crash in Evolution Mail: crash on exit


Summary:	crash in Evolution Mail: crash on exit


Status:	RESOLVED DUPLICATE of bug 523463

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.10.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:	2007-09-24 22:09 UTC by bugreports
Modified:	2009-05-20 06:15 UTC

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

Description bugreports 2007-09-24 22:09:49 UTC

What were you doing when the application crashed?
crash on exit


Distribution: Debian 3.1 (sarge)
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.23-rc7-sonne #4 SMP PREEMPT Thu Sep 20 07:47:58 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 184741888 vsize: 184741888 resident: 74997760 share: 21856256 rss: 74997760 rss_rlim: 4294967295
CPU usage: start_time: 1190663336 rtime: 4130 utime: 3803 stime: 327 cutime:11 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb681e6b0 (LWP 4408)]
[New Thread 0xaf546b90 (LWP 6690)]
[New Thread 0xb1095b90 (LWP 5234)]
[New Thread 0xb20ffb90 (LWP 5231)]
[New Thread 0xb18feb90 (LWP 4638)]
[New Thread 0xb2affb90 (LWP 4627)]
[New Thread 0xb341fb90 (LWP 4585)]
[New Thread 0xb3e2db90 (LWP 4577)]
[New Thread 0xb462eb90 (LWP 4576)]
[New Thread 0xb4e2fb90 (LWP 4575)]
[New Thread 0xb5649b90 (LWP 4570)]
0xb7f8f410 in __kernel_vsyscall ()

+ Trace 165201

Thread 2 (Thread 0xaf546b90 (LWP 6690))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/i686/cmov/libpthread.so.0
#2 _L_mutex_lock_86
from /lib/i686/cmov/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/cmov/libpthread.so.0
#4 segv_redirect
at main.c line 422
#5 <signal handler called>
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
#50 ??
#51 ??
#52 ??
#53 ??
#54 ??
#55 ??
#56 ??
#57 ??
#58 ??

Comment 1 Akhil Laddha 2008-05-02 10:32:08 UTC

Dup of bug 523463

Comment 2 Akhil Laddha 2009-05-20 06:15:24 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 523463 ***