GNOME Bugzilla – Bug 473302
crash in Tasks:
Last modified: 2007-09-24 16:39:17 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 151220224 vsize: 151220224 resident: 35569664 share: 19456000 rss: 35569664 rss_rlim: 4294967295 CPU usage: start_time: 1188684093 rtime: 18185 utime: 16106 stime: 2079 cutime:37895 cstime: 2890 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 -1208640784 (LWP 10569)] [New Thread -1279226992 (LWP 19544)] [New Thread -1301267568 (LWP 18334)] [New Thread -1266680944 (LWP 10596)] [New Thread -1243599984 (LWP 10594)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 160190
Thread 1 (Thread -1208640784 (LWP 10569))
----------- .xsession-errors (70 sec old) --------------------- (evolution:10569): libebook-CRITICAL **: e_book_async_open: assertion `book && E_IS_BOOK (book)' failed report junk?? qdraw report junk?? o-gnimoc report junk?? ognikep (evolution:10569): 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:10569): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa159360' (evolution:10569): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa159240' --------------------------------------------------
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 440422 ***