GNOME Bugzilla – Bug 478804
crash in Tasks: fgn
Last modified: 2007-10-07 09:47:00 UTC
What were you doing when the application crashed? fgn Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 137564160 vsize: 137564160 resident: 33607680 share: 21397504 rss: 33607680 rss_rlim: 4294967295 CPU usage: start_time: 1190355944 rtime: 521 utime: 465 stime: 56 cutime:0 cstime: 4 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208727840 (LWP 4178)] [New Thread -1236214896 (LWP 4196)] (no debugging symbols found) 0x007d6402 in __kernel_vsyscall ()
+ Trace 164283
Thread 1 (Thread -1208727840 (LWP 4178))
----------- .xsession-errors (18 sec old) --------------------- (evolution:4178): 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:4178): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a42008' (evolution:4178): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a42128' (evolution:4178): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca --------------------------------------------------
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 442949 ***