Bug 447412 – 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 447412 - 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-06-14 06:45 UTC by Dave
Modified:	2007-06-15 18:54 UTC

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

Description Dave 2007-06-14 06:45:47 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: 270061568 vsize: 270061568 resident: 44158976 share: 23035904 rss: 44158976 rss_rlim: 4294967295
CPU usage: start_time: 1181793086 rtime: 7664 utime: 6231 stime: 1433 cutime:82 cstime: 30 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 -1208830240 (LWP 25490)]
[New Thread -1261540464 (LWP 25576)]
[New Thread -1387656304 (LWP 25519)]
[New Thread -1282913392 (LWP 25509)]
(no debugging symbols found)
0x007b4402 in __kernel_vsyscall ()

+ Trace 140853

Thread 1 (Thread -1208830240 (LWP 25490))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
#6 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#7 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#8 ??
from /usr/lib/evolution/2.10/libetable.so.0
#9 e_tree_model_value_at
from /usr/lib/evolution/2.10/libetable.so.0
#10 e_table_sorting_utils_tree_sort
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 ??
from /usr/lib/evolution/2.10/libetable.so.0
#14 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 e_tree_model_node_changed
from /usr/lib/evolution/2.10/libetable.so.0
#20 e_tree_memory_thaw
from /usr/lib/evolution/2.10/libetable.so.0
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 bonobo_main
from /usr/lib/libbonobo-2.so.0
#28 main
#0 __kernel_vsyscall



----------- .xsession-errors (115 sec old) ---------------------
(evolution:25490): camel-WARNING **: Could not find key entry for word 'unknown00000000': Success
(evolution:25490): camel-WARNING **: Could not find key entry for word '0000000000': Success
(evolution:25490): camel-WARNING **: Could not find key entry for word 'unknown00000000': Success
(evolution:25490): camel-WARNING **: Could not find key entry for word '0000000000': Success
(evolution:25490): camel-WARNING **: Could not find key entry for word 'unknown00000000': Success
--------------------------------------------------

Comment 1 André Klapper 2007-06-14 11:39:29 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 431342 ***

Comment 2 Dave 2007-06-15 18:54:33 UTC

Thi has been resolved by updating to latest version, no more crashes!!!