GNOME Bugzilla – Bug 481504
crash in Tasks:
Last modified: 2007-10-01 14:35:39 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.20-2934.fc7xen #1 SMP Wed Sep 12 17:32:22 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: 191795200 vsize: 191795200 resident: 103366656 share: 34721792 rss: 103366656 rss_rlim: 4294967295 CPU usage: start_time: 1191040380 rtime: 2528 utime: 2303 stime: 225 cutime:153 cstime: 26 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208469792 (LWP 7001)] [New Thread -1293784176 (LWP 7446)] [New Thread -1304290416 (LWP 7144)] [New Thread -1327096944 (LWP 7080)] (no debugging symbols found) 0x0016e402 in __kernel_vsyscall ()
+ Trace 166336
Thread 2 (Thread -1293784176 (LWP 7446))
----------- .xsession-errors (267 sec old) --------------------- (evolution:7001): e-dateedit.c-WARNING **: time_text:14:00 (evolution:7001): e-dateedit.c-WARNING **: time_text:14:30 (evolution:7001): e-dateedit.c-WARNING **: time_text:14:00 (evolution:7001): e-dateedit.c-WARNING **: time_text:14:00 (evolution:7001): e-dateedit.c-WARNING **: time_text:14:30 (evolution:7001): e-dateedit.c-WARNING **: time_text:14:00 (evolution:7001): e-dateedit.c-WARNING **: time_text:14:30 (evolution:7001): e-data-server-ui-WARNING **: ENameSelectorDialog failed to open book! --------------------------------------------------
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 445309 ***