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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 426807

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-19 00:07 UTC by ptcesar4g
Modified:	2008-03-20 13:35 UTC

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

Description ptcesar4g 2008-01-19 00:07:28 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 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: 631017472 vsize: 631017472 resident: 55132160 share: 33001472 rss: 55132160 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200700745 rtime: 736 utime: 676 stime: 60 cutime:0 cstime: 2 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 46912496383344 (LWP 5274)]
[New Thread 1084496208 (LWP 6136)]
[New Thread 1189128528 (LWP 6132)]
[New Thread 1084229968 (LWP 5299)]
(no debugging symbols found)
0x0000003a0700d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 185896

Thread 1 (Thread 46912496383344 (LWP 5274))

#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_free_chain_with_offset
from /lib64/libglib-2.0.so.0
#7 ??
from /usr/lib64/evolution/2.10/plugins/liborg-gnome-plugin-manager.so
#8 g_datalist_clear
from /lib64/libglib-2.0.so.0
#9 g_object_unref
from /lib64/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#11 ??
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /lib64/libgobject-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 ??
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#21 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#22 ??
from /lib64/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#24 g_signal_emit
from /lib64/libgobject-2.0.so.0
#25 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#26 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#27 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#29 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#30 ??
from /lib64/libglib-2.0.so.0
#31 g_main_loop_run
from /lib64/libglib-2.0.so.0
#32 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#33 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Tobias Mueller 2008-03-20 13:35:23 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 426807 ***