GNOME Bugzilla – Bug 489507
crash in Tasks:
Last modified: 2007-10-24 06:43:23 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 242470912 vsize: 242470912 resident: 112967680 share: 63094784 rss: 112967680 rss_rlim: 4294967295 CPU usage: start_time: 1193162125 rtime: 2779 utime: 2603 stime: 176 cutime:0 cstime: 0 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 -1208183072 (LWP 6509)] [New Thread -1295926384 (LWP 6601)] [New Thread -1263932528 (LWP 6516)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 172303
Thread 1 (Thread -1208183072 (LWP 6509))
----------- .xsession-errors (196 sec old) --------------------- - had compilation errors. ----------------------------------------- CalDAV Eplugin starting up ... libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files (evolution:6509): 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:6509): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c93018' (evolution:6509): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c93138' (evolution:6509): e-data-server-ui-WARNING **: Key file does not have key 'imap:__carita@etch_' --------------------------------------------------
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 ***