GNOME Bugzilla – Bug 497420
crash in Tasks: Closing Evolution.
Last modified: 2007-11-16 19:45:01 UTC
Version: 2.10 What were you doing when the application crashed? Closing Evolution. 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 21:09:24 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: 142331904 vsize: 142331904 resident: 66940928 share: 39788544 rss: 66940928 rss_rlim: 4294967295 CPU usage: start_time: 1195228348 rtime: 12072 utime: 10579 stime: 1493 cutime:770 cstime: 1105 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 -1209132304 (LWP 8035)] [New Thread -1314923632 (LWP 9462)] [New Thread -1274000496 (LWP 8060)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178159
Thread 1 (Thread -1209132304 (LWP 8035))
----------- .xsession-errors (737 sec old) --------------------- ** (evolution:8035): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:8035): DEBUG: mailto URL program: evolution (evolution:8035): 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:8035): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa045008' (evolution:8035): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa045128' (evolution:8035): evolution-mail-WARNING **: Can't get contacts: EBookStatus returned 20 (evolution:8035): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:8035): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 447591 ***