GNOME Bugzilla – Bug 503364
crash in Tasks: sending an e-mail to som...
Last modified: 2008-03-20 13:35:42 UTC
Version: 2.10 What were you doing when the application crashed? sending an e-mail to someone. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 148160512 vsize: 148160512 resident: 57155584 share: 39264256 rss: 57155584 rss_rlim: 4294967295 CPU usage: start_time: 1197518159 rtime: 1090 utime: 994 stime: 96 cutime:33 cstime: 9 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 -1208518944 (LWP 2400)] [New Thread -1317270640 (LWP 2808)] [New Thread -1262486640 (LWP 2803)] [New Thread -1250772080 (LWP 2797)] [New Thread -1306780784 (LWP 2481)] [New Thread -1226790000 (LWP 2457)] [New Thread -1327760496 (LWP 2451)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 181730
Thread 1 (Thread -1208518944 (LWP 2400))
----------- .xsession-errors (241 sec old) --------------------- (evolution:2400): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:2400): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed (evolution:2400): e-dateedit.c-WARNING **: time_text:09:00 (evolution:2400): e-dateedit.c-WARNING **: time_text:09:00 (evolution:2400): e-dateedit.c-WARNING **: time_text:07:00 (evolution:2400): e-dateedit.c-WARNING **: time_text:07:00 (evolution:2400): e-dateedit.c-WARNING **: time_text:17:00 (evolution:2400): e-dateedit.c-WARNING **: time_text:07:00 --------------------------------------------------
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 426807 ***