Bug 509649 – crash in Tasks: viewing me calender

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 509649 - crash in Tasks: viewing me calender


Summary:	crash in Tasks: viewing me calender


Status:	RESOLVED DUPLICATE of bug 451144

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:	2008-01-15 14:21 UTC by fowlks
Modified:	2008-01-15 21:45 UTC

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

Description fowlks 2008-01-15 14:21:54 UTC

Version: 2.10

What were you doing when the application crashed?
viewing me calender


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 804122624 vsize: 804122624 resident: 125001728 share: 42647552 rss: 125001728 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199980098 rtime: 34117 utime: 32118 stime: 1999 cutime:264 cstime: 39 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 46912496399728 (LWP 21268)]
[New Thread 1084229968 (LWP 21310)]
[New Thread 1126455632 (LWP 21281)]
[New Thread 1126189392 (LWP 21280)]
[New Thread 1105209680 (LWP 21278)]
(no debugging symbols found)
0x0000003e56c0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 185436

Thread 1 (Thread 46912496399728 (LWP 21268))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_object_ref
from /lib64/libgobject-2.0.so.0
#4 e_cal_model_copy_component_data
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#5 calendar_control_sensitize_calendar_commands
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#6 ??
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#7 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#8 ??
from /lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#10 gtk_signal_emit
from /usr/lib64/libgtk-x11-2.0.so.0
#11 ??
from /usr/lib64/evolution/2.10/components/libevolution-calendar.so
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#14 ??
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /lib64/libgobject-2.0.so.0
#17 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#20 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#21 ??
from /lib64/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#23 g_signal_emit
from /lib64/libgobject-2.0.so.0
#24 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#25 ??
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#27 g_signal_emit
from /lib64/libgobject-2.0.so.0
#28 gtk_widget_grab_focus
from /usr/lib64/libgtk-x11-2.0.so.0
#29 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#30 bonobo_closure_invoke_va_list
from /usr/lib64/libbonobo-2.so.0
#31 bonobo_closure_invoke
from /usr/lib64/libbonobo-2.so.0
#32 ??
from /usr/lib64/libbonoboui-2.so.0
#33 Bonobo_UIComponent_execVerb
from /usr/lib64/libbonobo-2.so.0
#34 ??
from /usr/lib64/libbonoboui-2.so.0
#35 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#36 ??
from /lib64/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#38 g_signal_emit
from /lib64/libgobject-2.0.so.0
#39 ??
from /usr/lib64/libbonoboui-2.so.0
#40 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#41 ??
from /lib64/libgobject-2.0.so.0
#42 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#43 g_signal_emit_by_name
from /lib64/libgobject-2.0.so.0
#44 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#45 ??
from /lib64/libgobject-2.0.so.0
#46 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#47 g_signal_emit
from /lib64/libgobject-2.0.so.0
#48 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#49 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#50 ??
from /lib64/libgobject-2.0.so.0
#51 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#52 g_signal_emit
from /lib64/libgobject-2.0.so.0
#53 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#54 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#55 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#56 ??
from /lib64/libgobject-2.0.so.0
#57 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#58 g_signal_emit
from /lib64/libgobject-2.0.so.0
#59 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#60 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#61 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#62 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#63 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#64 ??
from /lib64/libglib-2.0.so.0
#65 g_main_loop_run
from /lib64/libglib-2.0.so.0
#66 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#67 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Bruno Boaventura 2008-01-15 21:45:56 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 451144 ***