Bug 450931 – 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 450931 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 444801

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-25 15:10 UTC by robert
Modified:	2007-07-02 00:10 UTC

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

Description robert 2007-06-25 15:10:22 UTC

Version: 2.10

What were you doing when the application crashed?



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.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:18:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 738611200 vsize: 738611200 resident: 112861184 share: 41451520 rss: 112861184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182699814 rtime: 7741 utime: 5129 stime: 2612 cutime:2 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496406112 (LWP 3389)]
[New Thread 1178904912 (LWP 21850)]
[New Thread 1105209680 (LWP 3484)]
[New Thread 1115965776 (LWP 3432)]
[New Thread 1094719824 (LWP 3428)]
(no debugging symbols found)
0x000000330d80d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 143593

Thread 1 (Thread 46912496406112 (LWP 3389))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
from /lib64/libglib-2.0.so.0
#4 ??
from /lib64/libglib-2.0.so.0
#5 ??
from /lib64/libglib-2.0.so.0
#6 g_slice_free1
from /lib64/libglib-2.0.so.0
#7 g_ptr_array_free
from /lib64/libglib-2.0.so.0
#8 camel_object_unref
from /usr/lib64/libcamel-1.2.so.10
#9 g_hash_table_foreach
from /lib64/libglib-2.0.so.0
#10 ??
from /usr/lib64/libcamel-1.2.so.10
#11 camel_object_unref
from /usr/lib64/libcamel-1.2.so.10
#12 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#13 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#15 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#16 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#17 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#18 ??
from /lib64/libglib-2.0.so.0
#19 g_main_loop_run
from /lib64/libglib-2.0.so.0
#20 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#21 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (36401 sec old) ---------------------
(evolution:3389): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:3389): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:3389): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:3389): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:3389): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:3389): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-07-02 00:10:43 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 444801 ***