GNOME Bugzilla – Bug 498036
crash in Tasks:
Last modified: 2007-11-20 06:38:09 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.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 642920448 vsize: 642920448 resident: 67272704 share: 41058304 rss: 67272704 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195419331 rtime: 1220 utime: 1088 stime: 132 cutime:25 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496412016 (LWP 28040)] [New Thread 1126189392 (LWP 28084)] [New Thread 1178904912 (LWP 28082)] [New Thread 1094719824 (LWP 28064)] (no debugging symbols found) 0x0000003b6ec0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 178600
Thread 1 (Thread 46912496412016 (LWP 28040))
----------- .xsession-errors --------------------- (evolution:28040): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:28040): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) BBDB spinning up... (evolution:28040): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8e1440' (evolution:28040): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8e0e40' camel-Message: -- camel-Message: -- camel-Message: -- Unmatched element: br warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff9c5fd000 --------------------------------------------------
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 464159 ***