GNOME Bugzilla – Bug 463485
crash in Tasks:
Last modified: 2007-08-22 20:52:30 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 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: 123768832 vsize: 123768832 resident: 44933120 share: 32706560 rss: 44933120 rss_rlim: 4294967295 CPU usage: start_time: 1186255655 rtime: 683 utime: 642 stime: 41 cutime:1 cstime: 6 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 -1208441120 (LWP 9261)] [New Thread -1252422768 (LWP 9326)] [New Thread -1231176816 (LWP 9286)] [New Thread -1219302512 (LWP 9284)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 152822
Thread 1 (Thread -1208441120 (LWP 9261))
----------- .xsession-errors (379 sec old) --------------------- (evolution:9261): e-dateedit.c-WARNING **: time_text:09:00 AM ** (gnome-help:9331): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (gnome-help:9331): WARNING **: IOR not set. ** (gnome-help:9331): WARNING **: Could not locate registry Unmatched element: br (evolution:9261): 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:9261): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8dee258' (evolution:9261): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8dee378' --------------------------------------------------
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 426807 ***