Bug 507168 – crash in Calendar: i am not sure. I am a fr...

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 507168 - crash in Calendar: i am not sure. I am a fr...


Summary:	crash in Calendar: i am not sure. I am a fr...


Status:	RESOLVED DUPLICATE of bug 431396

Product:	evolution
Classification:	Applications
Component:	Calendar
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-04 02:50 UTC by chinared725
Modified:	2008-01-24 11:59 UTC

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

Description chinared725 2008-01-04 02:50:20 UTC

Version: 2.10

What were you doing when the application crashed?
i am not sure. I am a freshman of Linux, I will be very happy if you give me some suggestions in using this wonderful system.


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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 149434368 vsize: 149434368 resident: 49655808 share: 35274752 rss: 49655808 rss_rlim: 4294967295
CPU usage: start_time: 1199414436 rtime: 1408 utime: 1292 stime: 116 cutime:1 cstime: 3 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 -1208568096 (LWP 4166)]
[New Thread -1285133424 (LWP 4276)]
[New Thread -1274643568 (LWP 4275)]
[New Thread -1232405616 (LWP 4210)]
[New Thread -1273959536 (LWP 4208)]
[New Thread -1221411952 (LWP 4185)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 183997

Thread 1 (Thread -1208568096 (LWP 4166))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free1
from /lib/libglib-2.0.so.0
#9 g_slist_free_1
from /lib/libglib-2.0.so.0
#10 g_slist_remove
from /lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#21 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#23 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#24 ??
from /usr/lib/libbonoboui-2.so.0
#25 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#26 g_closure_invoke
from /lib/libgobject-2.0.so.0
#27 ??
from /lib/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#29 g_signal_emit
from /lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/libbonoboui-2.so.0
#31 ??
from /usr/lib/libbonoboui-2.so.0
#32 bonobo_ui_xml_rm
from /usr/lib/libbonoboui-2.so.0
#33 bonobo_ui_engine_xml_rm
from /usr/lib/libbonoboui-2.so.0
#34 ??
from /usr/lib/libbonoboui-2.so.0
#35 _ORBIT_skel_small_Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#36 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#37 Bonobo_UIContainer_removeNode
from /usr/lib/libbonobo-2.so.0
#38 ??
from /usr/lib/libbonoboui-2.so.0
#39 bonobo_ui_component_rm
from /usr/lib/libbonoboui-2.so.0
#40 gal_view_menus_unmerge
from /usr/lib/evolution/2.10/libmenus.so.0
#41 ??
from /usr/lib/evolution/2.10/libmenus.so.0
#42 g_object_unref
from /lib/libgobject-2.0.so.0
#43 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#44 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#45 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#46 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#47 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#48 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#49 ??
from /lib/libglib-2.0.so.0
#50 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#51 ??
from /lib/libglib-2.0.so.0
#52 g_main_loop_run
from /lib/libglib-2.0.so.0
#53 bonobo_main
from /usr/lib/libbonobo-2.so.0
#54 main
#0 __kernel_vsyscall



----------- .xsession-errors (103 sec old) ---------------------
(evolution:4166): e-data-server-DEBUG: Loading categories from "/home/CHINARED/.evolution/categories.xml"
(evolution:4166): e-data-server-DEBUG: Loaded 29 categories
** (evolution:4166): WARNING **: aspell error: No word lists can be found for the language "zh_CN".
(evolution:4166): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:4166): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa4d4140'
(evolution:4166): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa4d4260'
(evolution:4166): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed
(evolution:4166): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed
--------------------------------------------------

Comment 1 Akhil Laddha 2008-01-24 11:59: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 431396 ***