Bug 454199 – crash in Tasks:

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 454199 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 431342

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-07-06 08:17 UTC by girish.tyagi
Modified:	2007-07-06 14:45 UTC

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

Description girish.tyagi 2007-07-06 08:17:45 UTC

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: 190472192 vsize: 190472192 resident: 74760192 share: 16392192 rss: 74760192 rss_rlim: 4294967295
CPU usage: start_time: 1183710107 rtime: 274 utime: 255 stime: 19 cutime:0 cstime: 1 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 -1208355104 (LWP 31688)]
[New Thread -1248285808 (LWP 31712)]
[New Thread -1258775664 (LWP 31711)]
[New Thread -1237795952 (LWP 31710)]
[New Thread -1227306096 (LWP 31707)]
(no debugging symbols found)
0x0082a402 in __kernel_vsyscall ()

+ Trace 146067

Thread 1 (Thread -1208355104 (LWP 31688))

#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 ??
from /usr/lib/evolution/2.10/libetable.so.0
#13 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 e_tree_model_node_changed
from /usr/lib/evolution/2.10/libetable.so.0
#19 e_tree_memory_thaw
from /usr/lib/evolution/2.10/libetable.so.0
#20 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 gtk_dialog_run
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libedataserverui-1.2.so.8
#28 ??
from /lib/libglib-2.0.so.0
#29 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#30 ??
from /lib/libglib-2.0.so.0
#31 g_main_loop_run
from /lib/libglib-2.0.so.0
#32 bonobo_main
from /usr/lib/libbonobo-2.so.0
#33 main
#0 __kernel_vsyscall



----------- .xsession-errors (283140 sec old) ---------------------
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3924): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-07-06 14:45:50 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 431342 ***