Bug 481549 – crash in Evolution Mail:

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


Summary:	crash in Evolution Mail:


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-09-29 10:05 UTC by halva
Modified:	2007-12-21 16:00 UTC

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

Description halva 2007-09-29 10:05:52 UTC

What were you doing when the application crashed?



Distribution: Debian 3.1 (sarge)
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 538927104 vsize: 538927104 resident: 46317568 share: 21372928 rss: 46317568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191060072 rtime: 904 utime: 816 stime: 88 cutime:4 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2ab74baef020 (LWP 16452)]
[New Thread 0x45009950 (LWP 16726)]
[New Thread 0x4604c950 (LWP 16585)]
[New Thread 0x44808950 (LWP 16569)]
[New Thread 0x44007950 (LWP 16568)]
[New Thread 0x43806950 (LWP 16567)]
[New Thread 0x43005950 (LWP 16566)]
[New Thread 0x42804950 (LWP 16515)]
[New Thread 0x42003950 (LWP 16489)]
[New Thread 0x41802950 (LWP 16483)]
[New Thread 0x41001950 (LWP 16482)]
[New Thread 0x40800950 (LWP 16481)]
0x00002ab743903c7f in waitpid () from /lib/libpthread.so.0

+ Trace 166377

Thread 2 (Thread 0x45009950 (LWP 16726))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 _L_mutex_lock_100
from /lib/libpthread.so.0
#2 pthread_mutex_lock
from /lib/libpthread.so.0
#3 <signal handler called>
#4 ??
#5 camel_object_trigger_event
at camel-object.c line 1511
#6 folder_changed_change
at camel-vee-folder.c line 1422
#7 session_thread_proxy
at camel-session.c line 530
#8 ??
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/libglib-2.0.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6
#12 ??



----------- .xsession-errors (59 sec old) ---------------------
** Message: Viewer spawned, PID 16676
** Message: GetValue variable 14 (e)
** Message: Initial window set, XID 2001820 size 200x70
** Message: No viewer proxy yet, deferring SetWindow
** Message: Viewer DBus interface name is 'org.gnome.totem.PluginViewer_16676'
** Message: NameOwnerChanged old-owner '' new-owner ':1.29'
** Message: Viewer now connected to the bus
** Message: ViewerSetup
** Message: Calling SetWindow
** Message: NameOwnerChanged old-owner '' new-owner ':1.29'
** Message: Already have owner, why are we notified again?
Viewer: SetWindow XID 33560608 size 200:70
** Message: Viewer state: STOPPED
** Message: SetWindow reply
** Message: ViewerReady
--------------------------------------------------

Comment 1 André Klapper 2007-12-21 16:00:00 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 ***