Bug 450703 – crash in Tasks: starting application

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 450703 - crash in Tasks: starting application


Summary:	crash in Tasks: starting application


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-06-24 18:43 UTC by colin
Modified:	2007-06-25 00:16 UTC

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

Description colin 2007-06-24 18:43:29 UTC

What were you doing when the application crashed?
starting application


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: Fedora

Memory status: size: 131837952 vsize: 131837952 resident: 27701248 share: 16203776 rss: 27701248 rss_rlim: 4294967295
CPU usage: start_time: 1182710587 rtime: 103 utime: 90 stime: 13 cutime:43 cstime: 6 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 -1208510752 (LWP 13076)]
[New Thread -1264403568 (LWP 13090)]
[New Thread -1284527216 (LWP 13086)]
[New Thread -1242567792 (LWP 13081)]
(no debugging symbols found)
0x00842402 in __kernel_vsyscall ()

+ Trace 143405

Thread 1 (Thread -1208510752 (LWP 13076))

#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 bonobo_main
from /usr/lib/libbonobo-2.so.0
#27 main
#0 __kernel_vsyscall



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

Comment 1 palfrey 2007-06-25 00:16:19 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 ***