GNOME Bugzilla – Bug 482411
crash in Calendar:
Last modified: 2007-10-02 03:35:52 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 173785088 vsize: 173785088 resident: 65568768 share: 49586176 rss: 65568768 rss_rlim: 4294967295 CPU usage: start_time: 1191284533 rtime: 806 utime: 750 stime: 56 cutime:47 cstime: 15 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 -1208551712 (LWP 6711)] [New Thread -1317926000 (LWP 6741)] [New Thread -1235735664 (LWP 6730)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 166990
Thread 1 (Thread -1208551712 (LWP 6711))
----------- .xsession-errors (207 sec old) --------------------- (evolution:6711): 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?) BBDB spinning up... (evolution:6711): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa6bb010' (evolution:6711): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa6bb130' (evolution:6711): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:6711): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed (evolution:6711): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:6711): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed --------------------------------------------------
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 444866 ***