Bug 442712 – 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 442712 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 434802

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-31 21:51 UTC by luiz.machado
Modified:	2007-12-21 15:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description luiz.machado 2007-05-31 21:51:30 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.16.18-cheetara #2 Thu Nov 9 10:42:51 BRST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: gnome

Memory status: size: 240599040 vsize: 240599040 resident: 81920000 share: 18935808 rss: 81920000 rss_rlim: 4294967295
CPU usage: start_time: 1180647859 rtime: 4150 utime: 4100 stime: 50 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232725408 (LWP 23589)]
[New Thread -1413481584 (LWP 23668)]
[New Thread -1352873072 (LWP 23653)]
[New Thread -1344484464 (LWP 23649)]
[New Thread -1326404720 (LWP 23648)]
[New Thread -1334793328 (LWP 23647)]
[New Thread -1317540976 (LWP 23619)]
[New Thread -1300358256 (LWP 23617)]
[New Thread -1309152368 (LWP 23616)]
[New Thread -1283187824 (LWP 23613)]
[New Thread -1274799216 (LWP 23612)]
[New Thread -1266410608 (LWP 23611)]
[New Thread -1257895024 (LWP 23610)]
[New Thread -1241019504 (LWP 23608)]
0xb77b6b11 in ?? () from /lib/libpthread.so.0

+ Trace 137090

Thread 8 (Thread -1300358256 (LWP 23617))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 _L_mutex_lock_88
from /lib/libpthread.so.0
#2 pthread_mutex_lock
from /lib/libpthread.so.0
#3 segv_redirect
at main.c line 436
#4 <signal handler called>
#5 ??
#6 folder_changed
at camel-vee-folder.c line 1461
#7 camel_object_trigger_event
at camel-object.c line 1504
#8 folder_changed_change
at camel-vee-folder.c line 1422
#9 session_thread_proxy
at camel-session.c line 530
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 pthread_setspecific
from /lib/libpthread.so.0
#15 ??
from /usr/lib/libglib-2.0.so.0
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
from /lib/libc.so.6
#21 ??
from /lib/libpthread.so.0
#22 ??
from /lib/libpthread.so.0
#23 ??
from /lib/libpthread.so.0
#24 ??

Comment 1 André Klapper 2007-12-21 15:56:57 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 434802 ***