GNOME Bugzilla – Bug 446181
crash in Tasks: setting up Evolution Mai...
Last modified: 2007-06-11 14:56:47 UTC
What were you doing when the application crashed? setting up Evolution Mail Preferences Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 130215936 vsize: 130215936 resident: 29638656 share: 17440768 rss: 29638656 rss_rlim: 4294967295 CPU usage: start_time: 1181501715 rtime: 3303 utime: 2921 stime: 382 cutime:1869 cstime: 155 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 -1208924448 (LWP 5369)] [New Thread -1267188848 (LWP 5386)] (no debugging symbols found) 0x00215402 in __kernel_vsyscall ()
+ Trace 139898
Thread 1 (Thread -1208924448 (LWP 5369))
----------- .xsession-errors (65 sec old) --------------------- (evolution:5369): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:5369): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 CalDAV Eplugin starting up ... (evolution:5369): 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:5369): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97ae018' (evolution:5369): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97ae138' (evolution:5369): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:5369): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:5369): 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 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 435356 ***