Bug 509654 – crash in Tasks: Disconnecting an IMAP fo...

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 509654 - crash in Tasks: Disconnecting an IMAP fo...


Summary:	crash in Tasks: Disconnecting an IMAP fo...


Status:	RESOLVED DUPLICATE of bug 324168

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-15 14:34 UTC by msoffen
Modified:	2008-04-10 08:14 UTC

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

Description msoffen 2008-01-15 14:34:03 UTC

Version: 2.10

What were you doing when the application crashed?
Disconnecting an IMAP folder.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 213536768 vsize: 213536768 resident: 102969344 share: 35033088 rss: 102969344 rss_rlim: 4294967295
CPU usage: start_time: 1200339227 rtime: 32383 utime: 30179 stime: 2204 cutime:80 cstime: 79 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 -1208977696 (LWP 2110)]
[New Thread -1297089648 (LWP 3583)]
[New Thread -1325438064 (LWP 2197)]
[New Thread -1286603888 (LWP 2134)]
[New Thread -1242739824 (LWP 2128)]
0x004ca991 in waitpid () from /lib/libpthread.so.0

+ Trace 185437

Thread 1 (Thread -1208977696 (LWP 2110))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#2 segv_redirect
at main.c line 408
#3 <signal handler called>
#4 pthread_mutex_lock
from /lib/libpthread.so.0
#5 camel_message_info_free
at camel-folder-summary.c line 2775
#6 vee_message_info_free
at camel-vee-summary.c line 45
#7 camel_message_info_free
at camel-folder-summary.c line 2792
#8 free_message_info
at camel-folder.c line 971
#9 camel_folder_free_message_info
at camel-folder.c line 989
#10 clear_info
at message-list.c line 2278
#11 IA__g_hash_table_foreach
at ghash.c line 662
#12 clear_tree
at message-list.c line 2297
#13 regen_list_done
at message-list.c line 2785
#14 mail_msg_idle_cb
at mail-mt.c line 480
#15 g_idle_dispatch
at gmain.c line 3928
#16 IA__g_main_context_dispatch
at gmain.c line 2045
#17 g_main_context_iterate
at gmain.c line 2677
#18 IA__g_main_loop_run
at gmain.c line 2881
#19 bonobo_main
from /usr/lib/libbonobo-2.so.0
#20 main
at main.c line 586
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (8 sec old) ---------------------
warning: the debug information found in "/usr/lib/debug//lib/libnss_files-2.6.so.debug" does not match "/lib/libnss_files.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gconv/ISO8859-1.so.debug" does not match "/usr/lib/gconv/ISO8859-1.so" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//lib/libnss_nisplus-2.6.so.debug" does not match "/lib/libnss_nisplus.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//lib/libnss_dns-2.6.so.debug" does not match "/lib/libnss_dns.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gconv/ISO8859-15.so.debug" does not match "/usr/lib/gconv/ISO8859-15.so" (CRC mismatch).
--------------------------------------------------

Comment 1 André Klapper 2008-04-10 08:14:16 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 324168 ***