GNOME Bugzilla – Bug 449174
crash in Tasks: Trying to check my excha...
Last modified: 2007-06-19 23:12:16 UTC
Version: 2.10 What were you doing when the application crashed? Trying to check my exchange account email after changing settings from No local copy to keeping local copies, I decided to quit instead and killed the program. 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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 151388160 vsize: 151388160 resident: 62459904 share: 36741120 rss: 62459904 rss_rlim: 4294967295 CPU usage: start_time: 1182268029 rtime: 1535 utime: 1415 stime: 120 cutime:3 cstime: 7 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 -1209006368 (LWP 11999)] [New Thread -1390122096 (LWP 12271)] [New Thread -1358652528 (LWP 12089)] (no debugging symbols found) 0x004f6402 in __kernel_vsyscall ()
+ Trace 142183
Thread 3 (Thread -1358652528 (LWP 12089))
----------- .xsession-errors (31 sec old) --------------------- (evolution:11999): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:11999): e-dateedit.c-WARNING **: time_text: 7:30 AM (evolution:11999): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:11999): e-dateedit.c-WARNING **: time_text:05:00 PM (evolution:11999): e-dateedit.c-WARNING **: time_text: 4:30 PM (evolution:11999): e-dateedit.c-WARNING **: time_text: 7:30 AM (evolution:11999): e-dateedit.c-WARNING **: time_text: 4:30 PM (evolution:11999): e-dateedit.c-WARNING **: time_text: 4:30 PM --------------------------------------------------
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 405646 ***