Bug 484784 – crash in Tasks: downloading email

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 484784 - crash in Tasks: downloading email


Summary:	crash in Tasks: downloading email


Status:	RESOLVED DUPLICATE of bug 442030

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

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-08 16:32 UTC by rstupart
Modified:	2007-10-30 04:36 UTC

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

Description rstupart 2007-10-08 16:32:46 UTC

Version: 2.10

What were you doing when the application crashed?
downloading email


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

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 173498368 vsize: 173498368 resident: 70103040 share: 45768704 rss: 70103040 rss_rlim: 4294967295
CPU usage: start_time: 1191857831 rtime: 3938 utime: 1853 stime: 2085 cutime:8 cstime: 56 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208301856 (LWP 2685)]
[New Thread -1366324336 (LWP 3410)]
[New Thread -1291080816 (LWP 2933)]
[New Thread -1290814576 (LWP 2704)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 168817

Thread 1 (Thread -1208301856 (LWP 2685))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libbonoboui-2.so.0
#11 ??
from /lib/libglib-2.0.so.0
#12 bonobo_ui_engine_dispose
from /usr/lib/libbonoboui-2.so.0
#13 ??
from /usr/lib/libbonoboui-2.so.0
#14 ??
#15 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#16 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#18 e_shell_close_all_windows
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 bonobo_main
from /usr/lib/libbonobo-2.so.0
#25 main
#0 __kernel_vsyscall



----------- .xsession-errors (8 sec old) ---------------------
(evolution:2685): e-table-CRITICAL **: e_tree_memory_node_get_data: assertion `path' failed
(evolution:2685): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed
(evolution:2685): e-table-CRITICAL **: e_tree_memory_node_set_data: assertion `path' failed
(evolution:2685): e-table-CRITICAL **: e_tree_memory_node_get_data: assertion `path' failed
(evolution:2685): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed
(evolution:2685): e-table-CRITICAL **: e_tree_memory_node_set_data: assertion `path' failed
(evolution:2685): camel-local-provider-WARNING **: Didn't get the next message where I expected (7795555) got 7780775 instead
(evolution:2685): camel-local-provider-WARNING **: Didn't get the next message where I expected (7795555) got 7780775 instead
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-30 04:36:14 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
the maintainers need more information to fix the bug. Could you please answer
the questions in the other report in order to help the developers?


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