Bug 576732 – crash in Evolution Mail and Calendar: Waiting for new letters ...

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 576732 - crash in Evolution Mail and Calendar: Waiting for new letters ...


Summary:	crash in Evolution Mail and Calendar: Waiting for new letters ...


Status:	RESOLVED DUPLICATE of bug 574940

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.26.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:	2009-03-25 14:43 UTC by Priit Laes (IRC: plaes)
Modified:	2009-03-26 03:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description Priit Laes (IRC: plaes) 2009-03-25 14:43:40 UTC

What were you doing when the application crashed?
Waiting for new letters to be downloaded/filtered


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.26.0 2009-03-20 (Gentoo)
BugBuddy Version: 2.26.0

System: Linux 2.6.28 #134 SMP PREEMPT Sat Dec 27 13:16:10 EET 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Compact
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 862736384 vsize: 862736384 resident: 67985408 share: 25538560 rss: 67985408 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237958997 rtime: 4926 utime: 4441 stime: 485 cutime:144 cstime: 75 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f50ce373750 (LWP 23907)]
[New Thread 0x7f50a0ba2950 (LWP 8998)]
[New Thread 0x7f509bfff950 (LWP 8997)]
[New Thread 0x7f50a54a0950 (LWP 8996)]
[New Thread 0x7f509b7fe950 (LWP 8995)]
[New Thread 0x7f50a19f3950 (LWP 8731)]
[New Thread 0x7f50a895a950 (LWP 23978)]
[New Thread 0x7f50b10ba950 (LWP 23977)]
[New Thread 0x7f50a5ea4950 (LWP 23929)]
[New Thread 0x7f50a66a5950 (LWP 23928)]
[New Thread 0x7f50a6ea6950 (LWP 23927)]
[New Thread 0x7f50a76a7950 (LWP 23926)]
[New Thread 0x7f50a7ea8950 (LWP 23925)]
[New Thread 0x7f50a921d950 (LWP 23924)]
[New Thread 0x7f50aadf1950 (LWP 23920)]
[New Thread 0x7f50ab5f2950 (LWP 23919)]
[New Thread 0x7f50abfff950 (LWP 23918)]
[New Thread 0x7f50b08b9950 (LWP 23917)]
[New Thread 0x7f50b1ae5950 (LWP 23914)]
[New Thread 0x7f50b22e6950 (LWP 23912)]
0x00007f50cb16d55f in __libc_waitpid (pid=8999, stat_loc=0x7fffd63c1d30, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 213846

Thread 6 (Thread 0x7f50a19f3950 (LWP 8731))

#0 __lll_lock_wait
at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 130
#1 _L_lock_102
from /lib/libpthread.so.0
#2 __pthread_mutex_lock
at pthread_mutex_lock.c line 86
#3 <signal handler called>
#4 message_info_to_db
at camel-folder-summary.c line 3386
#5 save_to_db_cb
at camel-folder-summary.c line 1451
#6 IA__g_hash_table_foreach
at ghash.c line 1210
#7 save_message_infos_to_db
at camel-folder-summary.c line 1508
#8 camel_folder_summary_save_to_db
at camel-folder-summary.c line 1552
#9 filter_free
at camel-folder.c line 2035
#10 session_thread_msg_free
at camel-session.c line 581
#11 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#12 g_thread_create_proxy
at gthread.c line 635
#13 start_thread
at pthread_create.c line 297
#14 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
#15 ??


evolution-mail-Message: Error occurred while existing dialogue active:
Hostiga localhost pole võimalik ühenduda: Connection refused
41	../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
--------------------------------------------------

Comment 1 Akhil Laddha 2009-03-26 03:56:48 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 574940 ***