Bug 446635 – crash in Tasks: Reading 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 446635 - crash in Tasks: Reading mail.


Summary:	crash in Tasks: Reading mail.


Status:	RESOLVED DUPLICATE of bug 436751

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-06-12 07:12 UTC by Ricardo Gladwell
Modified:	2007-06-12 16:13 UTC

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

Description Ricardo Gladwell 2007-06-12 07:12:09 UTC

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


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 155545600 vsize: 155545600 resident: 64491520 share: 49975296 rss: 64491520 rss_rlim: 4294967295
CPU usage: start_time: 1181629046 rtime: 639 utime: 575 stime: 64 cutime:50 cstime: 16 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 -1208449312 (LWP 2866)]
[New Thread -1332151408 (LWP 2925)]
[New Thread -1277178992 (LWP 2908)]
(no debugging symbols found)
0x00359402 in __kernel_vsyscall ()

+ Trace 140262

Thread 1 (Thread -1208449312 (LWP 2866))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#6 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#7 ??
from /usr/lib/evolution/2.10/libetable.so.0
#8 e_tree_model_value_at
from /usr/lib/evolution/2.10/libetable.so.0
#9 e_table_sorting_utils_tree_sort
from /usr/lib/evolution/2.10/libetable.so.0
#10 ??
from /usr/lib/evolution/2.10/libetable.so.0
#11 ??
from /usr/lib/evolution/2.10/libetable.so.0
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit
from /lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/evolution/2.10/libetable.so.0
#18 ethi_change_sort_state
from /usr/lib/evolution/2.10/libetable.so.0
#19 ??
from /usr/lib/evolution/2.10/libetable.so.0
#20 gnome_canvas_marshal_BOOLEAN__BOXED
from /usr/lib/libgnomecanvas-2.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /lib/libgobject-2.0.so.0
#23 ??
from /lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#25 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#27 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 ??
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 g_signal_emit
from /lib/libgobject-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgdk-x11-2.0.so.0
#38 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_loop_run
from /lib/libglib-2.0.so.0
#41 bonobo_main
from /usr/lib/libbonobo-2.so.0
#42 main
#0 __kernel_vsyscall



----------- .xsession-errors (25 sec old) ---------------------
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2866): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 palfrey 2007-06-12 16:13:37 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 436751 ***