Bug 509646 – crash in Tasks: I clicked Calendar and T...

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 509646 - crash in Tasks: I clicked Calendar and T...


Summary:	crash in Tasks: I clicked Calendar and T...


Status:	RESOLVED DUPLICATE of bug 447591

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

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

Description ptcesar4g 2008-01-15 14:08:50 UTC

Version: 2.10

What were you doing when the application crashed?
I clicked Calendar and Tasks within the Evolution Preferences dailog box


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: 635572224 vsize: 635572224 resident: 54915072 share: 32161792 rss: 54915072 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200395936 rtime: 778 utime: 718 stime: 60 cutime:0 cstime: 1 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 3856)]
[New Thread 1105475920 (LWP 7030)]
[New Thread 1094719824 (LWP 7026)]
[New Thread 1105209680 (LWP 3884)]
(no debugging symbols found)
0x0000003a0700d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 185434

Thread 1 (Thread 46912496383344 (LWP 3856))

#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_slist_remove
from /lib64/libglib-2.0.so.0
#8 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#9 gtk_window_remove_mnemonic
from /usr/lib64/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#11 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#12 ??
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit
from /lib64/libgobject-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib64/libgtk-x11-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 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#30 bonobo_socket_add_id
from /usr/lib64/libbonoboui-2.so.0
#31 bonobo_control_frame_get_remote_window
from /usr/lib64/libbonoboui-2.so.0
#32 ??
from /usr/lib64/libbonoboui-2.so.0
#33 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#34 ??
from /lib64/libgobject-2.0.so.0
#35 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#36 g_signal_emit
from /lib64/libgobject-2.0.so.0
#37 gtk_widget_realize
from /usr/lib64/libgtk-x11-2.0.so.0
#38 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#39 ??
from /usr/lib64/libgtk-x11-2.0.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
from /lib64/libgobject-2.0.so.0
#44 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#46 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#47 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#48 ??
from /lib64/libgobject-2.0.so.0
#49 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#50 g_signal_emit
from /lib64/libgobject-2.0.so.0
#51 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#53 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#54 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#55 ??
from /lib64/libgobject-2.0.so.0
#56 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#57 g_signal_emit
from /lib64/libgobject-2.0.so.0
#58 gtk_widget_map
from /usr/lib64/libgtk-x11-2.0.so.0
#59 gtk_widget_set_child_visible
from /usr/lib64/libgtk-x11-2.0.so.0
#60 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#61 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#62 ??
from /lib64/libgobject-2.0.so.0
#63 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#64 g_signal_emit
from /lib64/libgobject-2.0.so.0
#65 ??
from /usr/lib64/evolution/2.10/libemiscwidgets.so.0
#66 ??
from /lib64/libglib-2.0.so.0
#67 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#68 ??
from /lib64/libglib-2.0.so.0
#69 g_main_loop_run
from /lib64/libglib-2.0.so.0
#70 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#71 main
#0 waitpid
from /lib64/libpthread.so.0

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