GNOME Bugzilla – Bug 459690
crash in Tasks: exiting the program?
Last modified: 2007-07-29 18:08:52 UTC
Version: 2.10 What were you doing when the application crashed? exiting the program? 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.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 149979136 vsize: 149979136 resident: 57294848 share: 43339776 rss: 57294848 rss_rlim: 4294967295 CPU usage: start_time: 1185218900 rtime: 908 utime: 853 stime: 55 cutime:33 cstime: 10 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 -1209067808 (LWP 3935)] [New Thread -1353184368 (LWP 4163)] [New Thread -1308861552 (LWP 4162)] [New Thread -1263694960 (LWP 4033)] [New Thread -1274758256 (LWP 3992)] [New Thread -1252811888 (LWP 3971)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 150066
Thread 6 (Thread -1252811888 (LWP 3971))
----------- .xsession-errors (82 sec old) --------------------- (evolution:3935): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed (evolution:3935): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed (evolution:3935): e-dateedit.c-WARNING **: time_text:09:00 (evolution:3935): e-dateedit.c-WARNING **: time_text:09:00 (evolution:3935): e-dateedit.c-WARNING **: time_text:08:00 (evolution:3935): e-dateedit.c-WARNING **: time_text:08:00 (evolution:3935): e-dateedit.c-WARNING **: time_text:17:00 (evolution:3935): e-dateedit.c-WARNING **: time_text:08:00 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 432796 ***