Bug 604357 – crash in Evolution: Reading a 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 604357 - crash in Evolution: Reading a mail


Summary:	crash in Evolution: Reading a mail


Status:	RESOLVED DUPLICATE of bug 574940

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.28.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-12-11 10:34 UTC by Pascal Terjan
Modified:	2009-12-11 10:35 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description Pascal Terjan 2009-12-11 10:34:18 UTC

What were you doing when the application crashed?
Reading a mail


Distribution: Mandriva Linux release 2010.0 (Official) for i586
Gnome Release: 2.28.0 2009-10-22 (Mandriva)
BugBuddy Version: 2.28.0

System: Linux 2.6.31.6-desktop-2mnb #1 SMP Fri Nov 27 21:40:10 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: M
Icon Theme: Tango-Blue-Materia
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 233074688 vsize: 233074688 resident: 62648320 share: 18366464 rss: 62648320 rss_rlim: 18446744073709551615
CPU usage: start_time: 1260525663 rtime: 24638 utime: 13536 stime: 11102 cutime:7521 cstime: 6554 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb5b9b8f0 (LWP 7768)]
[New Thread 0xb3d3eb70 (LWP 16325)]
[New Thread 0xb353db70 (LWP 16324)]
[New Thread 0xae4edb70 (LWP 16323)]
[New Thread 0xab3ffb70 (LWP 16322)]
[New Thread 0xaca05b70 (LWP 7985)]
[New Thread 0xaeceeb70 (LWP 7787)]
[New Thread 0xaf4efb70 (LWP 7786)]
[New Thread 0xafcf0b70 (LWP 7785)]
[New Thread 0xb051ab70 (LWP 7784)]
[New Thread 0xb0d3ab70 (LWP 7780)]
[New Thread 0xb153bb70 (LWP 7779)]
[New Thread 0xb252fb70 (LWP 7778)]
[New Thread 0xb2d3cb70 (LWP 7776)]
[New Thread 0xb45c9b70 (LWP 7773)]
[New Thread 0xb4dcab70 (LWP 7772)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 219559

Thread 6 (Thread 0xaca05b70 (LWP 7985))

#0 __kernel_vsyscall
#1 __lll_lock_wait
from /lib/i686/libpthread.so.0
#2 _L_lock_657
from /lib/i686/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/libpthread.so.0
#4 <signal handler called>
#5 message_info_to_db
at camel-folder-summary.c line 3411
#6 save_to_db_cb
at camel-folder-summary.c line 1475
#7 IA__g_hash_table_foreach
at ghash.c line 1211
#8 save_message_infos_to_db
at camel-folder-summary.c line 1532
#9 camel_folder_summary_save_to_db
at camel-folder-summary.c line 1576
#10 filter_free
at camel-folder.c line 2015
#11 session_thread_msg_free
at camel-session.c line 576
#12 ms_thread_msg_free
at mail-session.c line 613
#13 camel_session_thread_msg_free
at camel-session.c line 689
#14 session_thread_proxy
at camel-session.c line 596
#15 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#16 g_thread_create_proxy
at gthread.c line 635
#17 start_thread
from /lib/i686/libpthread.so.0
#18 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 130



---- Critical and fatal warnings logged during execution ----

** camel **: camel_session_get_service: assertion `url_string != NULL' failed 
** camel **: camel_session_get_service: assertion `url_string != NULL' failed 


----------- .xsession-errors (221866 sec old) ---------------------
(galeon:6718): Gdk-WARNING **: XID collision, trouble ahead
(galeon:6718): Gdk-WARNING **: XID collision, trouble ahead
(galeon:6718): Gdk-WARNING **: XID collision, trouble ahead
(galeon:6718): Gdk-WARNING **: XID collision, trouble ahead
(galeon:6718): Gdk-WARNING **: XID collision, trouble ahead
(galeon:6718): Gdk-WARNING **: XID collision, trouble ahead
(galeon:6718): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Pascal Terjan 2009-12-11 10:35:46 UTC


*** This bug has been marked as a duplicate of bug 574940 ***